When we launched our free Agent Readiness Check, Stripe and GitLab both scored 68 out of 100. That was a strange result for two companies that ship official MCP servers. A commenter on r/mcp pointed out why: our check was looking in the wrong places.

Stripe's MCP server lives at mcp.stripe.com, and it's listed in the official MCP Registry as com.stripe/mcp. GitLab's is listed as com.gitlab/mcp, with its endpoint at gitlab.com/api/v4/mcp. (MCP Registry) Our check only looked for MCP signals on each company's main website, so it missed both.

Is your SaaS agent-ready? Get your score

So we fixed it. Here's what changed, what the new scores are, and what it tells you about where agents look for your MCP server.

What the check looks at now

Common subdomains. The check now tries mcp.<yourdomain> and api.<yourdomain>, the places people and clients tend to try first.

The official MCP Registry. The check searches the registry for your company and credits a server only if it's published under your domain's reverse-DNS namespace, such as com.stripe/* for stripe.com, or if its endpoint is on your domain. The registry only grants a namespace like that after the publisher proves it owns the domain. (MCP Registry docs) That matters, because a registry search for "stripe" returns 17 servers, and only one of them is Stripe's. Third-party wrappers that borrow your name don't count toward your score.

AI Catalog and Server Cards. With SEP-2127 now final, a client can read /.well-known/ai-catalog.json on your domain and follow it to a Server Card that describes your server before connecting. (SEP-2127) The check now reads the catalog and follows the URL it lists.

robots.txt, by name. Instead of a single pass or fail, the result now names each AI crawler your robots.txt blocks, such as GPTBot or ClaudeBot, and quotes the line that blocks it. That was another request from the r/mcp thread. The check covers 13 AI bots, and Stripe, GitLab and Resend all allow every one of them, so all three score 20 of 20 there.

The new scores

Site Before After What changed
gitlab.com 68 75 MCP went from 8/15 to 15/15, credited through com.gitlab/mcp in the official MCP Registry
stripe.com 68 75 MCP went from 8/15 to 15/15, found at mcp.stripe.com and in the registry as com.stripe/mcp
resend.com 85 85 MCP was already 15/15; the check now also finds mcp.resend.com and Resend's ai-catalog.json

Stripe and GitLab still lose points in two places. Neither publishes an OpenAPI spec where the check looks (0 of 20), and neither has an llms-full.txt alongside its llms.txt (15 of 20). Those are fixable in an afternoon, and they matter for the same reason: agents read them before they decide how to use you.

What this means for your SaaS

The lesson isn't really about Stripe. Agents and clients don't look in one place for your MCP server. They check the registry, a likely subdomain, and your domain's .well-known paths. If your server shows up in only one of them, some share of the agents looking for you won't find it, and they'll connect to whatever they can reach instead. That's ghost churn: no complaint, just work quietly routed somewhere else.

A quick checklist:

  • Publish your server to the official MCP Registry under your own domain's namespace, not a personal GitHub one.
  • Host it on, or redirect from, mcp.<yourdomain>.
  • Publish /.well-known/ai-catalog.json and a Server Card.
  • Check that your robots.txt isn't blocking the AI crawlers you actually want.

Thanks to the r/mcp commenters who pushed us on this. The check is better for it.

See where your product stands

Is your SaaS agent-ready? Get your score

Is your SaaS agent-ready? Get your score

Run a free Pryno readiness check on your MCP server