53/ 100
vc1.kz D
This site registers real WebMCP tools at runtime. There is significant room for improvement.
Scanned 1 day ago with Chrome 152, real execution with a modelContext interceptor and synthetic interaction.
Scan another site PASS Page loads over HTTPS 8/8 pts
The page answered with HTTP 200 over HTTPS.
PASS AI agents allowed in robots.txt 6/6 pts
No major AI crawler is blocked in robots.txt.
FAIL llms.txt present 0/4 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 4/4 pts
No noindex directive found.
PASS WebMCP tools detected at runtime 14/14 pts
10 tool(s) registered through modelContext.registerTool() while the page ran in our Chrome.
PART Tool schema quality 15/20 pts
Average schema quality 4.6/5 across 10 tool(s). Weakest: search_products (5/6), get_product (5/6), get_category (5/6), get_filter_names (5/6).
How to fix: Give every tool a clear description, a JSON Schema with typed and described parameters, constraints (enum, minLength, pattern, format), additionalProperties: false, and readOnlyHint annotations where they apply.
FAIL Origin Trial token 0/12 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/6 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/3 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/3 pts
No manifest to evaluate.
How to fix: Serve the manifest with the Content-Type: application/json header.
PASS Tools on more than the entry page 6/6 pts
All 10 checked pages expose tools.
FAIL The surface adapts to the page 0/14 pts
Every page exposes exactly the same tools, so nothing is tied to the current page.
How to fix: Add tools tied to the page the agent is on: the details of that product or service, that page form, search within the current section. The same tools everywhere is a header, not a capability.
Tools registered by this page
| Name | Description | Parameters | Read-only |
|---|---|---|---|
search_products | Searches the website product catalog by product name, model, brand, part number or technic... | 1 | no |
get_product | Returns information about a specific product from the website. | 1 | no |
get_category | Returns information about a specific product category from the website. | 1 | no |
get_filter_names | Returns the technical filter names available across the product catalog. | 0 | no |
filter_products | Filters products within a category using category-specific technical characteristics. | 2 | no |
compare_products | Compares multiple products from the website catalog. | 1 | no |
get_product_specs | Returns the technical specifications of a specific product. | 1 | no |
check_stock | Checks the current stock status of a specific product. | 1 | no |
add_to_cart | Adds a specified quantity of a product to the shopping cart. | 2 | no |
remove_from_cart | Removes a product from the shopping cart. | 1 | 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.