--- title: "AR-ACT-04: MCP server card | Agent Ready Checklist" description: "AR-ACT-04 (MAY, Act layer): MCP server card. What it asks, the evidence, the command that verifies it and the fix on 19 platforms." canonical: https://agentreadychecklist.com/checklist/ar-act-04 site: "Agent Ready Checklist" last_updated: 2026-11-05 section: "Checklist" --- # AR-ACT-04: MCP server card | Agent Ready Checklist > AR-ACT-04 (MAY, Act layer): MCP server card. What it asks, the evidence, the command that verifies it and the fix on 19 platforms. Source: https://agentreadychecklist.com/checklist/ar-act-04 Site: Agent Ready Checklist Last reviewed: 2026-11-05 Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search) Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free). # AR-ACT-04: MCP server card AR-ACT-04 is a MAY on the act layer: Ship an MCP server card for pre-connection discovery. It applies to products with an MCP server. 19 of 19 platforms have a recipe below, 10 of them workarounds. The kit check mcp-or-cli tests it with one command. 3 cited facts back it. ## The requirement Identifier AR-ACT-04 Level MAY Layer Act Applies to products with an MCP server Checked by Ora, matched on this site, Cloudflare mcpServerCard, Verify Kit mcp-or-cli Ora check [mcp-server-card](#ora) The statement Ship an MCP server card for pre-connection discovery. ## Why - The spec calls the server card an emerging convention (SEP-2127) and lists its path as an open question until the draft settles.primary source: [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md), read 2026-11-04 - Cloudflare checks /.well-known/mcp/server-card.json with serverInfo name and version, a transport endpoint and capabilities.primary source: [isitagentready.com/.well-known/agent-skills/mcp-server-card/SKILL.md](https://isitagentready.com/.well-known/agent-skills/mcp-server-card/SKILL.md), read 2026-11-04 - Cloudflare Radar found MCP Server Cards and API Catalogs together on fewer than 15 sites of its scanned set.primary source, 2026-04-17: [blog.cloudflare.com/agent-readiness/](https://blog.cloudflare.com/agent-readiness/), read 2026-11-04 ## How to verify ### [MCP server or CLI discoverable](https://agentreadychecklist.com/kit/mcp-or-cli/) ```bash curl -fsSL https://agentreadychecklist.com/kit/verify.sh | bash -s -- https://example.com --only=mcp-or-cli ``` Fetches /.well-known/mcp/server-card.json and /.well-known/mcp.json, POSTs an MCP initialize to /mcp, and, if the reader names a CLI package, checks the npm registry for it. PASS on any one. **It cannot prove:** Cannot judge whether the tools are useful or whether OAuth completes; a POST to /mcp is the one non-GET call and is skipped with --get-only. ### The one-line version curl -s /.well-known/mcp/server-card.json | jq -e ".serverInfo.name". ## Verify with Ora One check in Ora's catalogue (contract 1.38.0, read 2026-11-05) read this row. Each entry says what the check looks at and why this page lists it. - `mcp-server-card` MCP server-card.json Looks for a server card at the server URL or listed in /.well-known/ai-catalog.json, and still reads /.well-known/mcp/server-card.json for a site with one server, though the extension does not recommend that path. Usability, 2 points, bonus, recommended; catalogue applicability mcp. Listed because: same name, `server card`. ### Run just these checks ```bash curl -s -X POST https://ora.ai/api/scan/checks -H 'content-type: application/json' -d '{"url":"https://example.com","checkIds":["mcp-server-card"]}' ``` This calls the endpoint Ora documents for re-verifying a fix. It sends no cache, returns a result for each id and no total score, and spends one scan from the daily budget. Replace the URL with yours. [How to re-verify one fix](https://agentreadychecklist.com/guides/re-verify-one-fix-with-ora/). ### Or audit the whole site ```bash npx ax@0.10 audit https://example.com --min-score 70 ``` Exit code 1 means the score is below the number you passed, so the same line gates a deploy: [the CI recipe](https://agentreadychecklist.com/guides/gate-deploys-on-agent-readiness-in-ci/). [Why this site recommends Ora, and where it falls short](https://agentreadychecklist.com/verify-with-ora/). ## Fix it on your platform ### Next.js (App Router)recipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/nextjs-app-router/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. Next.js 16.x (npm latest 16.4.5, read 2026-11-04); docs at nextjs.org/docs/app. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Next.js (App Router) recipes](https://agentreadychecklist.com/platforms/nextjs-app-router/#ar-act-04) ### Astrorecipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/astro/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. Astro 7.x (npm latest astro 7.4.5, @astrojs/sitemap 3.7.4, read 2026-11-04). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Astro recipes](https://agentreadychecklist.com/platforms/astro/#ar-act-04) ### Nuxtrecipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/nuxt/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. Nuxt 4.x (npm latest nuxt 4.6.4, @nuxtjs/robots 7.0.2, @nuxtjs/sitemap 9.1.0, read 2026-11-04). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Nuxt recipes](https://agentreadychecklist.com/platforms/nuxt/#ar-act-04) ### SvelteKitrecipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/sveltekit/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. SvelteKit (npm latest @sveltejs/kit 3.1.1, read 2026-11-04); docs at svelte.dev/docs/kit. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All SvelteKit recipes](https://agentreadychecklist.com/platforms/sveltekit/#ar-act-04) ### Remix and React Router (framework mode)recipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/remix-react-router/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. React Router framework mode (npm latest react-router 8.5.1; Remix v2 @remix-run/node 2.17.5, read 2026-11-04); docs at reactrouter.com. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Remix and React Router (framework mode) recipes](https://agentreadychecklist.com/platforms/remix-react-router/#ar-act-04) ### Plain static hosting (Netlify, Vercel static, Cloudflare Pages, GitHub Pages, S3 and CloudFront)recipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/static-hosting/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. Host documentation as published on 2026-11-04 (no version numbers; config files \_headers, \_redirects, vercel.json, 404.html). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Plain static hosting (Netlify, Vercel static, Cloudflare Pages, GitHub Pages, S3 and CloudFront) recipes](https://agentreadychecklist.com/platforms/static-hosting/#ar-act-04) ### WordPress and Elementorrecipe Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/wordpress-elementor/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. WordPress 7.1.4 (core release from the version-check API), Elementor 4.3.6 (plugin directory, updated 2026-11-02), Yoast SEO 28.8 noted for llms.txt; docs read 2026-11-04. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All WordPress and Elementor recipes](https://agentreadychecklist.com/platforms/wordpress-elementor/#ar-act-04) ### Shopify (Online Store 2.0 themes)workaround Shopify publishes the business profile for UCP discovery at /.well-known/ucp on the merchant storefront ({shop}.myshopify.com/.well-known/ucp) rather than an MCP server card, and the root path /.well-known/mcp/server-card.json is not one a merchant can serve. Workaround: host a card on your own API domain and link it from the site. Hosted SaaS, Online Store 2.0 Liquid themes, docs read 2026-11-04; storefront behaviour probed live on one Shopify store the same day. Derived from Shopify's documentation read on 2026-11-04. [shopify.dev/docs/agents/profiles](https://shopify.dev/docs/agents/profiles) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Shopify (Online Store 2.0 themes) recipes](https://agentreadychecklist.com/platforms/shopify/#ar-act-04) ### Webflowworkaround Serve the card the way the AR-FIND-04 recipe serves the catalog (/platforms/webflow/#ar-find-04), at /.well-known/mcp/server-card.json. Publish it only if you run an MCP server. Hosted SaaS, help center articles read 2026-11-04 (updated dates 2024-10-14 to 2026-10-29). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Webflow recipes](https://agentreadychecklist.com/platforms/webflow/#ar-act-04) ### Framerworkaround This platform builds no MCP server, so the card would describe a server you host elsewhere. Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/framer/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. Hosted SaaS, help articles read 2026-11-04 (marked updated 2026-09-15). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Framer recipes](https://agentreadychecklist.com/platforms/framer/#ar-act-04) ### Wix (Wix Editor and Wix Studio)workaround The Wix AR-FIND-04 entry (/platforms/wix/#ar-find-04) says Wix-managed hosting has no file upload at /.well-known/, so a server card cannot be placed there. Workaround: serve /.well-known/mcp/server-card.json from a domain you control, as that entry says for the catalog. Hosted SaaS, help center read 2026-11-04. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Wix (Wix Editor and Wix Studio) recipes](https://agentreadychecklist.com/platforms/wix/#ar-act-04) ### Squarespace (version 7.1)workaround Squarespace's developer documentation covers the Commerce APIs and the Custom Code Specification, and describes no way to run a request handler on a site. Not possible on this platform without outside help. Workaround: serve /.well-known/mcp/server-card.json from your root domain or a proxy in front of the platform, as the AR-FIND-04 recipe does for the catalog (/platforms/squarespace/#ar-find-04). Hosted SaaS, version 7.1 sites, help center read 2026-11-04 (articles updated 2026-07-17 to 2026-11-03). Derived from Squarespace's documentation read on 2026-11-04. [developers.squarespace.com/custom-code](https://developers.squarespace.com/custom-code) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Squarespace (version 7.1) recipes](https://agentreadychecklist.com/platforms/squarespace/#ar-act-04) ### HubSpot CMS (Content Hub)workaround Host the card file somewhere you control and create a URL redirect from /.well-known/mcp/server-card.json to it, as the AR-FIND-04 recipe does for the catalog (/platforms/hubspot-cms/#ar-find-04); a validator that needs a direct 200 at that path will not accept the redirect. Hosted SaaS, Content Hub, knowledge base and developer docs read 2026-11-04. Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All HubSpot CMS (Content Hub) recipes](https://agentreadychecklist.com/platforms/hubspot-cms/#ar-act-04) ### Docusaurusworkaround This platform builds no MCP server, so the card would describe a server you host elsewhere. Place the card at /.well-known/mcp/server-card.json the same way the AR-FIND-04 recipe places the AI Catalog (/platforms/docusaurus/#ar-find-04), and give it a serverInfo.name that matches your MCP server. Publish it only if you run an MCP server. 3.10.2 (npm @docusaurus/core latest, read 2026-11-04). Generic step from the AgentReady specification; not platform-specific. [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Docusaurus recipes](https://agentreadychecklist.com/platforms/docusaurus/#ar-act-04) ### Mintlifyrecipe Mintlify generates the server card for its automatic MCP server at /.well-known/mcp/server-card.json (its AR-ACT-03 recipe); there is nothing to write. A card for a server of your own would sit beside it. Hosted SaaS, docs read 2026-11-04. Derived from Mintlify's documentation read on 2026-11-04. [mintlify.com/docs/ai/model-context-protocol](https://mintlify.com/docs/ai/model-context-protocol) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Mintlify recipes](https://agentreadychecklist.com/platforms/mintlify/#ar-act-04) ### GitBookworkaround The documentation read lists no server card for GitBook's MCP endpoint at ~gitbook/mcp. Workaround: serve /.well-known/mcp/server-card.json from your root domain or a proxy, as the AR-FIND-04 recipe does for the catalog (/platforms/gitbook/#ar-find-04). Hosted SaaS, docs read 2026-11-04. Derived from GitBook's documentation read on 2026-11-04. [gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs](https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All GitBook recipes](https://agentreadychecklist.com/platforms/gitbook/#ar-act-04) ### ReadMerecipe Turn on the MCP Server Card setting; ReadMe publishes the card for its MCP server (its AR-FIND-04 recipe). Hosted SaaS, docs read 2026-11-04. Derived from ReadMe's documentation read on 2026-11-04. [docs.readme.com/main/docs/ai-discoverability](https://docs.readme.com/main/docs/ai-discoverability) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All ReadMe recipes](https://agentreadychecklist.com/platforms/readme/#ar-act-04) ### Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront)workaround Serve the card the way the AR-FIND-04 recipe serves the catalog (/platforms/salesforce-commerce-cloud/#ar-find-04): add the file to ssrShared and an app.get route for /.well-known/mcp/server-card.json in ssr.js. Publish it only if you run an MCP server. Hosted SaaS (B2C Commerce help release 264.0.0); PWA Kit retail-react-app 10.3.0 and pwa-kit-runtime 3.21.0 on npm, read 2026-11-04. Derived from Salesforce B2C Commerce's documentation read on 2026-11-04. [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront) recipes](https://agentreadychecklist.com/platforms/salesforce-commerce-cloud/#ar-act-04) ### Adobe Commerce and Magento Open Sourceworkaround Serve the card the way the AR-FIND-04 recipe serves the catalog (/platforms/adobe-commerce/#ar-find-04), at /.well-known/mcp/server-card.json. The Adobe Commerce 2.4.9 release notes read list no MCP server, so the card describes a server you host elsewhere. 2.4.9 (GitHub tag published 2026-05-12; 2.4.10-alpha1 tagged 2026-10-13); release notes read 2026-11-04. Derived from Adobe Commerce and Magento Open Source's documentation read on 2026-11-04. [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9) and [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md). [All Adobe Commerce and Magento Open Source recipes](https://agentreadychecklist.com/platforms/adobe-commerce/#ar-act-04) ## What it does not do - The path may move; the spec does not pin one yet. - A card does not prove the server responds. ## Common mistakes - Card lists tools the server no longer exposes. - Relative endpoint that resolves against the wrong host. ## Related - Term: [.well-known](https://agentreadychecklist.com/glossary/well-known/) - Term: [MCP server](https://agentreadychecklist.com/glossary/mcp-server/) - Term: [MCP server card](https://agentreadychecklist.com/glossary/mcp-server-card/) ## Sources - [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)read 2026-11-04 - [isitagentready.com/.well-known/agent-skills/mcp-server-card/SKILL.md](https://isitagentready.com/.well-known/agent-skills/mcp-server-card/SKILL.md)read 2026-11-04 - [blog.cloudflare.com/agent-readiness/](https://blog.cloudflare.com/agent-readiness/)read 2026-11-04 - [shopify.dev/docs/agents/profiles](https://shopify.dev/docs/agents/profiles)read 2026-11-04 - [developers.squarespace.com/custom-code](https://developers.squarespace.com/custom-code)read 2026-11-04 - [mintlify.com/docs/ai/model-context-protocol](https://mintlify.com/docs/ai/model-context-protocol)read 2026-11-04 - [gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs](https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs)read 2026-11-04 - [docs.readme.com/main/docs/ai-discoverability](https://docs.readme.com/main/docs/ai-discoverability)read 2026-11-04 - [developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/create-a-sitemap.html)read 2026-11-04 - [experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9](https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/magento-open-source/2-4-9)read 2026-11-04 - [modelcontextprotocol.io](https://modelcontextprotocol.io/)read 2026-11-04 - [ora.ai/api/checks, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=requirement)read 2026-11-05 - [ora.ai/llms-full.txt](https://ora.ai/llms-full.txt?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=requirement)read 2026-11-05 - [registry.npmjs.org/ax, the ax README](https://registry.npmjs.org/ax)read 2026-11-05 Verify with Ora The scanner this site recommends for the whole checklist. 132 checks, a score out of 100, no account. `npx ax@0.10 audit --min-score ` [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/) Fix it on - [Next.js (App Router)recipe](#p-nextjs-app-router) - [Astrorecipe](#p-astro) - [Nuxtrecipe](#p-nuxt) - [SvelteKitrecipe](#p-sveltekit) - [Remix and React Router (framework mode)recipe](#p-remix-react-router) - [Plain static hosting (Netlify, Vercel static, Cloudflare Pages, GitHub Pages, S3 and CloudFront)recipe](#p-static-hosting) - [WordPress and Elementorrecipe](#p-wordpress-elementor) - [Shopify (Online Store 2.0 themes)workaround](#p-shopify) - [Webflowworkaround](#p-webflow) - [Framerworkaround](#p-framer) - [Wix (Wix Editor and Wix Studio)workaround](#p-wix) - [Squarespace (version 7.1)workaround](#p-squarespace) - [HubSpot CMS (Content Hub)workaround](#p-hubspot-cms) - [Docusaurusworkaround](#p-docusaurus) - [Mintlifyrecipe](#p-mintlify) - [GitBookworkaround](#p-gitbook) - [ReadMerecipe](#p-readme) - [Salesforce B2C Commerce (SFRA and PWA Kit / Composable Storefront)workaround](#p-salesforce-commerce-cloud) - [Adobe Commerce and Magento Open Sourceworkaround](#p-adobe-commerce) Last reviewed 2026-11-05. AgentReady v2.0, read 2026-11-04.