Free tool · no signup · runs now
MCP server card checker
The server card tells agents what your MCP server offers and where to reach it. The checker validates the same card the audit requires.
Part of the AI agent trust checker group — also included in the free full scan.
Checks site-wide files at the domain root — any page URL on the domain gives the same result.
One free scan · anonymous preview · sign in to save the full report
server-cards: 1 (audit)Static example for MCP server card checker; run the check above for your own result.What it checks
See whether agents can connect to your MCP server through a valid card.
Named entries, non-empty remotes; falls back to ai-catalog.json entries.
Reads the raw JSON only, never renders. Follows up to 5 redirects.
What good looks like
Good looks like named entries with non-empty remotes — a card an agent can actually connect through. Nameless or remoteless cards fail; missing files report na.
How to fix it
Serve server-cards.json with named entries carrying remotes, or an ai-catalog.json index.
What the full scan adds
- All 34 checks in one pass — one URL, every category, a single report.
- Evidence on every row: the values found, why it fails, the fix, and a deep link per check.
- Your score against the global distribution — see where you stand.
- Sign in and the report is kept for 1 year; anonymous reports expire after 7 days.
Official source: SEP-2127, MCP server card · Rule: agent-readiness v1 · checker library
Tracking a Google update? Run the update impact check or read the search update radar.
Frequently asked questions
Is the MCP server card checker free?
Yes — one free run without an account, with an anonymous preview. Sign in to save the full report and keep the evidence.
How often should I run it?
After every deploy that touches routing, templates or the checked file — and after each Google core update, to confirm nothing regressed.
Does the check run JavaScript?
No — it reads the no-JS response only, exactly what a crawler or AI agent sees when it fetches the URL.
How is this different from a full audit?
This page runs one check with its full criteria and fix notes. The free full scan runs every category at once and keeps the evidence per URL — use it once you know which checks matter.
What is MCP server discovery?
Discovery is how an agent finds your MCP server before it can use the card: an ai-catalog.json index or a registry entry that points at server-cards.json. This checker validates the card and falls back to ai-catalog.json entries when the card is missing; discovery is what makes either one findable.
What is an MCP server card?
A small JSON document listing named MCP entries and the remote endpoints agents connect to. It is the contract between your server and an agent runtime: a named entry with a non-empty remote is usable, a nameless or remoteless entry is not.