Falling behind.

My website nytimes.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/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.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/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.com registers WebMCP tools but serves no Chrome origin-trial token, so the modelContext API does not exist for real Chrome users (Chrome 149-156 gates WebMCP behind an origin trial).

Task: register the site's origin for the WebMCP origin trial at https://developer.chrome.com/origintrials, then serve the token on every page that registers tools — either <meta http-equiv="origin-trial" content="TOKEN"> in the <head>, or an Origin-Trial HTTP response header. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.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/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.com's homepage has no labeled forms. Without WebMCP tools, well-labeled semantic forms are what browser agents fall back to for taking actions.

Task: audit the site's key interactive flows and ensure each form uses real <form> elements with <label for=...> bound to every input (not placeholder-only, not div-with-onclick). Keep markup semantic: correct input types, a submit button, and descriptive button text. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.com's robots.txt blocks AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, Claude-User). Blocked crawlers cannot read, cite, or recommend the site in AI search and agent workflows.

Task: review robots.txt and remove the blanket Disallow rules for AI user-agents (GPTBot, ClaudeBot, Claude-User, Google-Extended, PerplexityBot) unless a specific section genuinely must stay private — in that case scope the Disallow to those paths only. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.com has no /llms.txt. llms.txt is a curated markdown map that tells LLMs what a site is and where its key content lives (spec: https://llmstxt.org).

Task: create /llms.txt as static markdown: an H1 with the site name, a one-paragraph summary, then sections linking the site's most important pages with one-line descriptions each. Keep it under ~200 lines, factual, and free of marketing fluff. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.

My website nytimes.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/nytimes.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.