Here are a few more:

- https://smithery.ai/

- https://github.com/wong2/awesome-mcp-servers

- http://mcp.so/servers

- https://cursor.directory/mcp

But as mentioned above, there is an ongoing discussion for the Anthropic registry https://github.com/modelcontextprotocol/registry

Instead of connecting to a server with 1000(s) of tools, I'm going the opposite direction and claim that you only need <10 sharp tools/small function for most use cases.

As an example, today I re-implemented Google's AlphaEvolve with <7 tools (https://toolkami.com/alphaevolve-toolkami-style/).

I can't wait for first-party remote MCP servers to become more common. Right now we're taking a strange detour of everyone trying to proxy everyone else's APIs and do manual API Key juggling because platforms aren't running their own MCP servers and clients don't support the latest OAuth changes.

In a year from now, Github will run a single public Github MCP server that you will connect to via OAuth - you won't need to install it locally or faff around with tokens or environment variables at all.

I’ve been seeing MCP compared to extensions in web browsers. Which I find telling, since I wouldn’t exactly say web extensions have been a great success - it’s a pretty niche dev market, and the security posture remains pretty anxiety inducing

There's some movement on https://github.com/modelcontextprotocol/registry

> The MCP Registry service provides a centralized repository for MCP server entries. It allows discovery and management of various MCP implementations with their associated metadata, configurations, and capabilities.