Static agent-operability evidence
Agent Readiness Checker
Inspect whether a page exposes understandable links, buttons, form controls, landmarks, and early WebMCP signals. No opaque score and no claim that a browser agent can complete the workflow.
Why static evidence first?
Native links, buttons, labels, names, and form semantics are durable signals for both people and agents. Runtime focus behavior, authentication, challenges, and JavaScript-generated controls need a real browser and are deliberately outside this MVP.
Experimental WebMCP evidence
The current WebMCP Community Group draft defines imperative tools through document.modelContext.registerTool(). Declarative WebMCP is still unfinished, so this checker only reports matching source references found in inline scripts. It does not claim runtime WebMCP conformance.