Fix guides ยท Emerging standards

Publish an MCP server card

Optional, for sites running an MCP server: publish a server card so clients can discover it before connecting.

Proposal or draft, no proven ranking benefit

What we check

We fetch /.well-known/mcp/server-card.json and /.well-known/ai-catalog.json, and pass if either returns a non-empty JSON object.

6%

of 198 sites we could read pass this.

Why it matters

This is still evolving. The original proposal, SEP-1649, used /.well-known/mcp/server-card.json and moved to SEP-2127, which has been merged and lists .well-known/ai-catalog.json for pre-connection discovery. Server cards remain in the discussion, and sites are publishing at both paths.

It's only relevant if you run an MCP server. Most sites don't need this.

How to fix it

  1. Read SEP-2127 for the current format.
  2. Publish your server's details over HTTPS, as application/json.

Fix it yourself with AI

Small fixes shouldn't sit in a queue. Give your AI agent one prompt, and it fixes and deploys for you.

PromptShip is made by the team behind this checker.

Sources

Fixed it?

Run your site through the checker, and re-check after you ship to see what improved.

Check my site

Related guides