# 39,000 MCP Servers and Counting: Agents Now Have a Discovery Problem

*Noden blog · 2026-10-10 · https://getnoden.com/blog/39000-mcp-servers-discovery-problem*

A year ago the complaint was that agents had too few tools. That complaint is over.

## The numbers

The official registry for Model Context Protocol servers listed **39,238 servers on 4 October 2026**, according to a tracker that reads the registry's public API daily. That is up 45% in 30 days. The registry took until January to pass 1,500 servers, then added 11,902 in September alone, more than in its first nine months combined.

Other directories are large too. The same tracker counts more than 18,000 servers on Smithery.

## Quantity is not the same as quality

An analysis of the registry published in September made three points worth knowing:

- **Listing is not vetting.** Being in the official registry says a server exists, not that it is safe or good.
- **Much of it is opaque.** More than a third of remote servers offer an endpoint and a description, with no code to read.
- **The best-known servers are often missing.** Many of the servers people reach for first are not published there.

So an agent searching by keyword gets back hundreds of look-alike results with little to tell them apart.

## What an agent needs to choose well

A person picks tools using reputation, reviews and gut feeling. An agent needs the same signals in a form it can read:

1. **A clear contract.** What goes in, what comes out, in a schema.
2. **A price,** stated before the call.
3. **A track record.** Success rate and typical response time from real use.
4. **A consequence for failure.** If the output is wrong, the agent should not pay.

Registries supply the first item at best. The rest is the job of a marketplace.

## Registries and marketplaces do different jobs

Think of a registry as a phone book and a marketplace as a shop. The phone book tells you who exists. The shop shows a price, takes payment, and gives a refund when the goods are faulty. Agents need both.

## Practical advice

- **Publish to the official registry** so you can be found, then list where buyers can see price and track record.
- **Before installing anything with file or network access,** check who maintains it and whether the code is readable.
- **Let agents choose at run time** from a short, trusted catalog instead of a huge open one.

Noden lists each capability with its price, schema and verification status, and only charges when the output passes its check. [Browse the catalog](https://shop.getnoden.com).

## Sources

- [MCP adoption statistics, Gravity](https://gravity.fast/data/mcp-adoption-statistics/)
- [The MCP registry by the numbers, DEV Community](https://dev.to/amareswer/the-mcp-registry-by-the-numbers-38nc)
- [MCP registries in 2026, compared, DEV Community](https://dev.to/skillselion/mcp-registries-in-2026-compared-one-is-canonical-one-is-huge-and-almost-none-can-tell-you-what-147l)