How the score works
Availability gates the score: a page no in-browser agent can use gets no number. What passes the gate is scored on four pillars: Shared experience, Task completion, Tool quality, Trust, out of 100.Shared experienceweight 30
People and agents share this page. We grade the page a person actually sees and whether they can see what the agent does, so a site cannot score well by serving agents and no one else.Task completionweight 25
Could an agent get a task done here. We give an agent the tasks a site of this kind exists for and check it picks the right tool with the right arguments, and that the tool set covers the job.Tool qualityweight 25
Are the tool contracts built right. Valid schemas, descriptions that say what comes back, names an agent can tell apart, handlers behind every tool.Trustweight 20
Can an agent trust what the tools declare. Read-only hints that match what the tool actually says it does, and metadata that describes tools instead of steering the agent reading it. The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.Entering the OpenAI WebMCP Challenge? An audit here reviews three of its judging dimensions with evidence from a real browser. Originality and end-to-end execution still take human review.