Live score · last scanned 2026-08-29 · 1 scan recorded · static analysis
WebMCP tools registered
No WebMCP registration found in page HTML or script bundles.
Fix — Register page capabilities with document.modelContext.registerTool() so browser agents can act on your site instead of guessing at your UI.
My website target.com has no WebMCP tools registered. WebMCP (the W3C draft at https://webmachinelearning.github.io/webmcp/, shipping behind a Chrome origin trial and supported in the ChatGPT desktop browser) lets a page expose typed tools that AI agents can call instead of guessing at the UI.
Task: identify the 2-3 core actions a visitor performs on this site (e.g. search, check availability, get pricing, submit an inquiry) and register each as a WebMCP tool on page load:
document.modelContext.registerTool({
name: 'search_products', // snake_case, specific
description: 'Search the catalog; returns names, prices and URLs.', // written FOR the model: what it does, when to call it, what it returns
inputSchema: { type: 'object', properties: { query: { type: 'string' } }, required: ['query'] },
async execute({ query }) { /* call the site's existing search endpoint and return JSON */ }
});
Guard for environments without the API (if (!('modelContext' in document)) use the @mcp-b/global polyfill or return early). Wire execute() to existing endpoints — do not invent new backend functionality. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Declarative form tools
No declarative WebMCP form annotations found.
Fix — Annotate key forms with toolname/tooldescription attributes — the zero-JS path to expose them as agent tools.
My website target.com has HTML forms but none are annotated as declarative WebMCP tools. The WebMCP draft defines a zero-JavaScript path: annotate a form with toolname/tooldescription attributes and agents can invoke it as a structured tool. Task: find the site's most important forms (search, contact, booking, newsletter) and add declarative tool attributes, e.g.: <form toolname="contact_sales" tooldescription="Send a message to the sales team; expects name, email and message." action="/contact" method="post"> Keep names snake_case and descriptions written for an AI model (what it does + what it expects). Do not change form behavior for human users. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Chrome origin-trial token
Origin-trial token present.
MCP server card (.well-known)
No MCP server card found at /.well-known/mcp/server-card.json.
Fix — Publish a server card so agents can discover your backend MCP server, if you have one.
My website target.com serves no MCP server card. Agents probe /.well-known/mcp/server-card.json to discover whether a site offers a backend MCP server. Task: if the site has (or should advertise) an MCP endpoint, publish a valid JSON server card at /.well-known/mcp/server-card.json describing it (name, description, endpoint URL, transport). If there is no MCP server, this check is optional — skip it rather than publishing a card that points nowhere. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Actionable HTML (forms with labels)
Forms with labels found — agents can fall back to structured actuation.
robots.txt present
robots.txt found.
AI crawlers allowed
No blanket blocks on major AI crawlers.
XML sitemap
Sitemap found.
Canonical URL
Canonical tag present.
llms.txt
llms.txt found.
llms-full.txt
No /llms-full.txt.
Fix — Optionally serve llms-full.txt with full flattened content for LLM ingestion.
My website target.com serves /llms.txt but no /llms-full.txt. llms-full.txt is the companion file with full flattened content for LLM ingestion. Task: generate /llms-full.txt containing the full markdown content of the site's key pages (docs, guides, product pages) concatenated under clear H1/H2 headings, ideally regenerated at build time so it never goes stale. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Content readable without JavaScript
~2,599 chars of server-rendered text (ratio 1%).
Semantic structure (main/article + h1)
Semantic landmarks found.
Schema.org JSON-LD
Valid JSON-LD found (types: WebPage).
OpenGraph metadata
og:title and og:description present.
Meta description
Missing or trivial meta description.
Fix — Write a 120–160 char description that states what the page does.
My website target.com's pages are missing substantive meta descriptions. Task: add a unique <meta name="description"> of 120-160 characters to every indexable page stating concretely what the page does or offers — no keyword stuffing, no boilerplate repeated across pages. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Descriptive title
“Target : Expect More. Pay Less.”
HTTPS
Served over HTTPS.
No mixed content
No insecure subresources detected.
Permissions-Policy declared
No Permissions-Policy header.
Fix — Declare a Permissions-Policy; WebMCP tool exposure is governed by the "tools" policy (default self).
My website target.com sends no Permissions-Policy header. WebMCP tool exposure is governed by this policy (the "tools" directive, default self), and declaring one signals deliberate configuration. Task: add a Permissions-Policy response header at the server/CDN layer declaring the powerful features the site actually uses and disabling the rest, e.g.: geolocation=(), microphone=(), camera=(). When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/target.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Fix everything with AI
One prompt covering all 6 failing checks — paste it into Claude Code, Cursor, or any coding agent pointed at your site's repository.
You are working on the website target.com. An agent-readiness scan (https://webmcp-ai.dev/score/target.com) scored it 70/100. Fix the following 6 failing checks, in order. Work through them one at a time, committing after each. Where a fix touches robots.txt, llms.txt, meta tags or JSON-LD, generate content from the site's real pages — never placeholder text. 1. [Agent capabilities] WebMCP tools registered Finding: No WebMCP registration found in page HTML or script bundles. Fix: Register page capabilities with document.modelContext.registerTool() so browser agents can act on your site instead of guessing at your UI. 2. [Agent capabilities] Declarative form tools Finding: No declarative WebMCP form annotations found. Fix: Annotate key forms with toolname/tooldescription attributes — the zero-JS path to expose them as agent tools. 3. [Agent capabilities] MCP server card (.well-known) Finding: No MCP server card found at /.well-known/mcp/server-card.json. Fix: Publish a server card so agents can discover your backend MCP server, if you have one. 4. [Content accessibility] llms-full.txt Finding: No /llms-full.txt. Fix: Optionally serve llms-full.txt with full flattened content for LLM ingestion. 5. [Machine comprehension] Meta description Finding: Missing or trivial meta description. Fix: Write a 120–160 char description that states what the page does. 6. [Trust & security] Permissions-Policy declared Finding: No Permissions-Policy header. Fix: Declare a Permissions-Policy; WebMCP tool exposure is governed by the "tools" policy (default self). Standards to follow: the W3C WebMCP draft (https://webmachinelearning.github.io/webmcp/) for tool registration, https://llmstxt.org for llms.txt, and Schema.org for JSON-LD. When done, re-scan at https://webmcp-ai.dev/score/target.com and confirm the score improved.
Share & embed
Put your score on your site or README. The badge always shows this domain's latest score and links back here:
<a href="https://webmcp-ai.dev/score/target.com"><img src="https://webmcp-ai.dev/badge/target.com.svg" width="230" height="44" alt="target.com agent readiness score 70/100 (C) — webmcp-ai.dev" /></a>
Monitor this domain
Agent-readiness standards move fast — Chrome trials, ChatGPT's browser, new checks. Get a weekly rescan of target.com by email with score changes flagged. Free, unsubscribe anytime.
On a free 25-minute strategy call we walk through these results live and map the exact WebMCP tools target.com should register — prioritized, with a roadmap you can hand to a developer.