Live score · last scanned 2026-08-30 · 2 scans recorded · static analysis
monday.com
“The AI Work Platform for People & Agents | monday.com”
▲ +2 since previous scan
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 monday.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/monday.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 monday.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/monday.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 monday.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/monday.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
No /llms-full.txt.
Fix — Optionally serve llms-full.txt with full flattened content for LLM ingestion.
My website monday.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/monday.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Content readable without JavaScript
~16,362 chars of server-rendered text (ratio 3%).
Semantic structure (main/article + h1)
Missing <main>/<article> landmark or <h1>.
Fix — Use semantic landmarks and a single clear h1 so machines can segment your page.
My website monday.com's pages lack semantic structure — no <main>/<article> landmark and/or no <h1>. Machines segment pages by landmarks and heading hierarchy. Task: wrap primary content in <main> (one per page), use <article>/<section>/<nav> where appropriate, and give every page exactly one specific <h1> with a logical h2/h3 hierarchy below it. When you are done, verify the fix by re-scanning at https://webmcp-ai.dev/score/monday.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Schema.org JSON-LD
Valid JSON-LD found (types: Organization, SoftwareApplication, WebSite, 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 monday.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/monday.com (or POST the URL to https://webmcp-ai.dev/api/scan) and confirm the check now passes.
Descriptive title
“The AI Work Platform for People & Agents | monday.com”
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 monday.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/monday.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 7 failing checks — paste it into Claude Code, Cursor, or any coding agent pointed at your site's repository.
You are working on the website monday.com. An agent-readiness scan (https://webmcp-ai.dev/score/monday.com) scored it 77/100. Fix the following 7 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. 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. [Content accessibility] Semantic structure (main/article + h1) Finding: Missing <main>/<article> landmark or <h1>. Fix: Use semantic landmarks and a single clear h1 so machines can segment your page. 6. [Machine comprehension] Meta description Finding: Missing or trivial meta description. Fix: Write a 120–160 char description that states what the page does. 7. [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/monday.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/monday.com"><img src="https://webmcp-ai.dev/badge/monday.com.svg" width="230" height="44" alt="monday.com agent readiness score 77/100 (B) — webmcp-ai.dev" /></a>
Monitor this domain
Agent-readiness standards move fast — Chrome trials, ChatGPT's browser, new checks. Get a weekly rescan of monday.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 monday.com should register — prioritized, with a roadmap you can hand to a developer.