AI Product Index / MCP server card published

MCP server card published

The discovery route for tool-using agents. If you run an MCP server, this is how a client finds it without being handed a URL by a human.

How to pass it

If you run an MCP server, publish a server card so clients can find it without being handed a URL. The specs disagree on the path — SEP-2127 says /.well-known/mcp.json, Cloudflare reads /.well-known/mcp/server-card.json — so serve both.

Check your own site

Free, no signup, same endpoint that produced every grade on the leaderboard:

curl "https://index.percall.dev/api/score?url=https://your-site.example"

It returns the letter grade and every check by name with pass/fail. The $0.05 call at POST /api/audit adds why each one failed and a snippet with your origin already in it.

The rest of the checklist

6 more 2026 checks, and 13 from the other generation.

• llms.txt published 15 pts
• llms.txt has a title and summary 5 pts
• llms-full.txt published 5 pts
• robots.txt published 5 pts
• AI crawlers not blocked 10 pts
• sitemap.xml published 8 pts
• schema.org JSON-LD on the page 15 pts
• title and meta description 7 pts
• Open Graph tags 7 pts
• canonical URL declared 5 pts
• machine-readable alternates advertised 8 pts
• agent card at /.well-known/agent-card.json 10 pts
• served over HTTPS 5 pts
• Content Signals declared in robots.txt 3 pts
• A2A card at the 1.0 path 3 pts
• API catalog (RFC 9727) 2 pts
• Agent Skills index 2 pts
• Serves markdown to callers that ask for it 3 pts
• Web Bot Auth key directory 2 pts