Live score · last scanned 2026-08-30 · 1 scan recorded · static analysis
WebMCP tools registered
Found WebMCP API usage in page HTML (“navigator.modelContext”).
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 telnyx.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/telnyx.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Chrome origin-trial token
No WebMCP origin-trial token found (Chrome 149–156 requires one in production).
Fix — Request a WebMCP origin-trial token at developer.chrome.com/origintrials and serve it via meta tag or header.
My website telnyx.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/telnyx.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
MCP server card (.well-known)
Valid JSON at /.well-known/mcp/server-card.json.
Actionable HTML (forms with labels)
No labeled forms detected on the homepage.
Fix — Even without WebMCP, well-labeled semantic forms are what agents fall back to.
My website telnyx.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/telnyx.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
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
llms-full.txt found.
Content readable without JavaScript
~17,357 chars of server-rendered text (ratio 4%).
Semantic structure (main/article + h1)
Semantic landmarks found.
Schema.org JSON-LD
Valid JSON-LD found (types: Organization, WebSite, WebPage, BreadcrumbList, SoftwareApplication, Service).
OpenGraph metadata
og:title and og:description present.
Meta description
Substantive meta description present.
Descriptive title
“Infrastructure for realtime agents | Telnyx”
HTTPS
Served over HTTPS.
No mixed content
No insecure subresources detected.
Permissions-Policy declared
Permissions-Policy header present.
Fix everything with AI
One prompt covering all 3 failing checks — paste it into Claude Code, Cursor, or any coding agent pointed at your site's repository.
You are working on the website telnyx.com. An agent-readiness scan (https://webmcp-ai.dev/score/telnyx.com) scored it 88/100. Fix the following 3 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] 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. 2. [Agent capabilities] Chrome origin-trial token Finding: No WebMCP origin-trial token found (Chrome 149–156 requires one in production). Fix: Request a WebMCP origin-trial token at developer.chrome.com/origintrials and serve it via meta tag or header. 3. [Agent capabilities] Actionable HTML (forms with labels) Finding: No labeled forms detected on the homepage. Fix: Even without WebMCP, well-labeled semantic forms are what agents fall back to. 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/telnyx.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/telnyx.com"><img src="https://webmcp-ai.dev/badge/telnyx.com.svg" width="230" height="44" alt="telnyx.com agent readiness score 88/100 (A) — webmcp-ai.dev" /></a>Monitor this domain
Agent-readiness standards move fast — Chrome trials, ChatGPT's browser, new checks. Get a weekly rescan of telnyx.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 telnyx.com should register — prioritized, with a roadmap you can hand to a developer.