24/ 100
expertai.ro F
No WebMCP integration was detected at runtime. There is significant room for improvement.
Scanned 9 hours ago with Chrome 150, real execution with a modelContext interceptor and synthetic interaction. Scan another site
PASS Page loads over HTTPS 10/10 pts
The page answered with HTTP 200 over HTTPS.
PASS AI agents allowed in robots.txt 8/8 pts
No major AI crawler is blocked in robots.txt.
FAIL llms.txt present 0/6 pts
No usable llms.txt found.
How to fix: Publish /llms.txt: a plain-text overview of the site (purpose, key pages, tools, contact) that AI models can read cheaply.
PASS Not blocked by noindex 6/6 pts
No noindex directive found.
FAIL WebMCP tools detected at runtime 0/20 pts
No registerTool() call was observed and no form carries declarative WebMCP attributes. We executed the page, scrolled and simulated input, so deferred and delayed scripts had their chance to run.
How to fix: Register tools with modelContext.registerTool() (prefer document.modelContext with a navigator.modelContext fallback), or annotate forms with the official declarative attributes: toolname, tooldescription, toolautosubmit and toolparamdescription on fields.
N/A Tool schema quality 0/15 pts
No tools to evaluate.
How to fix: Expose at least one tool first.
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.
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.
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.
Want WebMCP working on your site?
GOAI implements WebMCP end to end: imperative tools, valid schemas, the origin trial token and the discovery manifest.