WebMCP validation that actually executes your page
Static checkers read your HTML and guess. We load your site in a real Chrome browser, intercept the modelContext API before any script runs, and report the tools your page truly registers. Deferred, bundled and base64-encoded scripts included.
Real execution
A headless HTML grep cannot see registerTool() inside a deferred or base64-wrapped bundle. Our Chrome runs your page, scrolls it and simulates input, then records every tool registration that actually happens.
Spec-accurate checks
We test the attributes and APIs that exist in the official Chrome documentation: toolname, tooldescription, toolparamdescription, modelContext, and the origin trial token. Nothing invented.
Honest scoring
Community conventions such as the /.well-known/webmcp manifest are labeled as unofficial and scored as a bonus. What cannot be measured remotely is stated, not failed.
Why most WebMCP checkers get it wrong
- WebMCP tools exist only inside a real browser tab. A scanner that never executes your JavaScript reports zero tools for perfectly working sites.
- Performance plugins defer and base64-encode scripts, so searching the HTML for "registerTool" finds nothing even when tools work.
- There is no manifest, no data-toolname and no toolaction in the official spec. Checkers that fail you on invented attributes measure nothing.
- While WebMCP is in origin trial, a valid token is what makes tools work in stable Chrome. Almost nobody checks it. We decode and verify it.
Recent scans
| Website | Score | Grade | When |
|---|---|---|---|
| www.seodr.ro | 80/100 | B | 1 hour ago |
| www.asigurari.biz | 100/100 | A+ | 2 hours ago |
| www.seodns.ro | 57/100 | C | 3 hours ago |
| pcalba.ro | 100/100 | A+ | 5 hours ago |
| www.goai.ro | 100/100 | A+ | 6 hours ago |
Want WebMCP working on your site?
GOAI implements WebMCP end to end: imperative tools, valid schemas, the origin trial token and the discovery manifest. Already live on 40+ production sites.