Can an AI agent find the MCP server I run?
If you run an MCP server, the connector that lets AI assistants use your product directly, a server card is its listing: what it does, which tools it offers and where to connect. We look for one at the addresses agents check. If you do not run an MCP server, you have nothing to publish here.
What it actually is
The Model Context Protocol is how assistants such as Claude plug into outside services: search your docs, book a slot, send an email. A server card is the label on that plug. It is a small JSON file on your site that names the server, describes it and points to the endpoint, so an agent can learn what is on offer before it connects.
Why it matters
An MCP server nobody can find is a door with no sign. Without a card, a person has to hear about your server somewhere and wire it in by hand. With one, an agent arriving at your domain can see that you offer tools, read what they do, and offer to use them, which is the whole point of having built the server.
What good looks like
One server card per MCP server you operate, served as real JSON from your own domain, whose name, description and endpoint match the server that actually answers, and which is updated when the tools change rather than left describing last year's version.
Being honest about it
This is an Advanced check, so it never fails a page and stays out of your headline score. Most websites do not run an MCP server, and for them a warning here is the expected result, not a defect. The format is also still settling: the proposal that defines it is a draft, and sites in the wild publish it in more than one place, so we accept any of the established ones.
Where most sites go wrong
The usual gap is a company that launched an MCP server and announced it in a blog post, but never published anything on its domain that a machine could find. The other is a card that drifted: it names an endpoint that moved, or a site that answers every unknown address with its homepage, so a card appears to exist and is really an HTML page.
On the web
State of the Web · November 2026In November 2026, 1% of the sites we could read passed the “MCP Server Card” check.
Next.js sites pass it most often, at 4%. WordPress sites pass it least often, at 0%.
On the sites scanned in both October 2026 and November 2026, it stayed at 12%.
The month-by-month line counts the sites scanned in each calendar month, so it can differ from the figure above, which uses each site’s latest scan from the last three months.
Goes with
-
Sites that pass this are 3.5 times as likely to pass the “Open Graph tags for sharing” check too. 67% of the sites that pass the first check pass this one, against 20% of the sites that do not.
-
Sites that pass this are 3 times as likely to pass the “llms.txt is present and valid” check too. 80% of the sites that pass the first check pass this one, against 28% of the sites that do not.
-
Sites that pass this are twice as likely to pass the “Organization schema with sameAs” check too. 67% of the sites that pass the first check pass this one, against 33% of the sites that do not.
Not enough history yet.
Based on the sites Bot Appétit has scanned. Most of these sites come from lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call