Runs your page in a real browser. No guessing. Blog Leaderboard RO EN
57/ 100

www.seodns.ro C

This site registers real WebMCP tools at runtime. Overall readiness is moderate.

Scanned 5 hours ago with Chrome 150, real execution with a modelContext interceptor and synthetic interaction. Scan another site

Agent access22 / 30
PASS Page loads over HTTPS 10/10 pts
The page answered with HTTP 200 over HTTPS.
FAIL AI agents allowed in robots.txt 0/8 pts
robots.txt blocks: gptbot, claudebot, anthropic-ai, ccbot, google-extended, bytespider, meta-externalagent.
How to fix: Remove Disallow rules that target AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and similar) or that block the whole site.
PASS llms.txt present 6/6 pts
Found llms.txt (6,461 bytes).
PASS Not blocked by noindex 6/6 pts
No noindex directive found.
WebMCP tools, measured in a real browser35 / 50
We load the page in Chrome, intercept modelContext before any script runs and record what your page actually registers.
PASS WebMCP tools detected at runtime 20/20 pts
4 tool(s) registered through modelContext.registerTool() while the page ran in our Chrome.
PASS Tool schema quality 15/15 pts
Average schema quality 5/5 across 4 tool(s).
FAIL Origin Trial token 0/15 pts
No origin-trial token found. While WebMCP is in origin trial, stable Chrome only exposes modelContext to origins that serve a valid token.
How to fix: Register your origin at developer.chrome.com/origintrials for the WebMCP trial and serve the token in a meta http-equiv="origin-trial" tag. Without it, stable Chrome does not expose modelContext to your visitors while the API is in trial.
Discovery, community conventions0 / 20
Not part of the official Chrome spec. Scored as a small bonus because static crawlers and directories use it.
FAIL Discovery manifest at /.well-known/webmcp 0/10 pts
No valid JSON at /.well-known/webmcp (status 404).
How to fix: Publish a JSON file at /.well-known/webmcp describing your tools. It is not part of the official spec, but it lets crawlers and static tools discover what your site offers.
FAIL Manifest describes tools 0/5 pts
The manifest does not describe any tools.
How to fix: Add a "tools" array with name, description and inputSchema for each tool.
FAIL Manifest served as application/json 0/5 pts
No manifest to evaluate.
How to fix: Serve the manifest with the Content-Type: application/json header.

Tools registered by this page

NameDescriptionParametersRead-only
search_site Cauta (search) continut pe site-ul Servicii SEO dupa un termen. 1 yes
get_site_info Informatii (site info) despre site-ul Servicii SEO. Optional, filtreaza pe sectiune. 1 yes
get_pages Paginile (pages) principale ale site-ului Servicii SEO. Optional, filtreaza dupa un cuvant... 1 yes
request_quote Trimite o cerere de oferta sau de contact (request a quote) catre Servicii SEO. Foloseste... 5 no

Captured live from modelContext.registerTool() calls while the page ran. A static HTML scan cannot see these.

Not measurable remotely, so not scored: end-to-end tool execution by an agent, human-in-the-loop consent handling, and result quality. Test those with the Model Context Tool Inspector extension in a WebMCP-capable Chrome.

Push this score higher?

GOAI implements WebMCP end to end: imperative tools, valid schemas, the origin trial token and the discovery manifest.

Talk to GOAI