The official MCP Registry crossed the 50,000 mark in late October. Tanod's weekly count put it at 49,672 servers on October 25, up 4,053 (8.9%) in a single week, with 2,848 new publisher namespaces. (Tanod) Two days later, ProtocolProbe's daily pull counted 51,168, with 724 new servers added since the day before. (ProtocolProbe)

That's good news for MCP. It's harder news for any SaaS team that assumed shipping an MCP server was the finish line.

Is your SaaS agent-ready? Get your score

Listed isn't the same as found

Search the registry for "stripe" today and you get 17 results. Only one of them, com.stripe/mcp, pointing to https://mcp.stripe.com, is published under Stripe's own domain. The rest are third-party wrappers, checkout helpers and personal projects that happen to use the name. (MCP Registry search)

Now picture an agent, or a developer setting one up, trying to connect to your product. If your name brings back a dozen lookalikes, the one they pick may not be yours. And if they can't find an official server at all, they'll either use someone else's wrapper or move on to a competitor that's easier to reach. That's ghost churn: the customer never complains, they just quietly stop routing work through you.

The four places agents look

There's no single discovery standard yet, so clients and agents check several places. Covering all four is cheap, and each one closes a gap the others leave open.

1. The official MCP Registry, under your own namespace. The registry ties a server's name to how its publisher proved who they are. Sign in with GitHub and your server must be named io.github.<username>/*. Prove you own a domain and you can publish as com.yourcompany/*. (MCP Registry docs) That domain-based name is the one signal in a crowded search result that says "this is the real one." If your server is listed under a personal GitHub account, it looks just like every unofficial wrapper around it.

2. A predictable subdomain. mcp.<yourdomain> is becoming the place people try first. Stripe's server lives at mcp.stripe.com, and Linear's at mcp.linear.app. A subdomain you control also means your customers' connections don't depend on anyone else's hosting staying around. (We covered why that matters in Don't let your MCP server live only in someone else's directory.)

3. The .well-known paths on your main domain. MCP Server Cards are now a final part of the spec. A client can read /.well-known/ai-catalog.json on your domain and follow it to a Server Card that describes your server, its endpoint and how to authenticate, before it ever connects. (SEP-2127) This is what lets an agent go from "acme.com" to your MCP server without a search step at all. (More in MCP Server Cards are final.)

4. llms.txt. This is a proposed convention, not part of MCP: a plain markdown file at /llms.txt that gives language models a short map of your docs. (llmstxt.org) It doesn't replace the other three, but it's where a model reading your site learns that an MCP server exists and where your setup guide is. If you have one, mention your MCP server and link its docs.

A quick audit for this week

  • Search the MCP Registry for your company name and count how many results aren't yours.
  • If your official server isn't there, or is listed under a personal io.github.* name, republish it under your domain's namespace.
  • Check that mcp.<yourdomain> either serves your MCP server or redirects to wherever it does live.
  • Publish /.well-known/ai-catalog.json and a Server Card.
  • Add your MCP server and its docs link to /llms.txt.

See where your product stands

Our free Agent Readiness Check scans your site for the signals AI agents look for and gives you a score in about a minute.

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