
MCP Registry Search
This server turns the official MCP registry into a queryable API. It exposes three tools: list_mcp_servers for paginated browsing, get_mcp_server_details to pull full metadata by reverse-DNS name, and search_mcp_registry for keyword lookups. You'd use this when building agents that need to discover other MCP servers at runtime instead of hardcoding integrations, or when you want to search by plain names rather than wrestling with reverse-DNS identifiers. It's also useful for registry auditing or building meta-agents that route requests to different MCP servers dynamically. No auth required, just point your client at the streamable-http endpoint and start querying.
- GitHub stars
- 1
- tools
- 3
- transport
- HTTP
- last updated
- May 16, 2026
Install
From registry metadata$ npx add-mcp https://mcpregistrysearchwilfredleejr.vercel.app/api/mcp --name mcp-registry-searchRun in your terminal. add-mcp asks which agents to add it to (Claude Code, Codex, Cursor and more). Add -g to install it for every project.
Review the command, arguments and environment values before installing. MCP servers run with your local permissions.
Other ways
Claude Code
$ claude mcp add --transport http mcp-registry-search https://mcpregistrysearchwilfredleejr.vercel.app/api/mcpRun in your terminal. Add --scope user to make it available in every project.
Tools
Verified live · 3 toolsVerified live against the running server on Nov 6, 2026.
search_mcp_registryFind servers by keyword or name (e.g. 'weather', 'github', 'database'). Returns matching servers with their endpoint URL, transport type, and description.2 params
Find servers by keyword or name (e.g. 'weather', 'github', 'database'). Returns matching servers with their endpoint URL, transport type, and description.
limitintegerquery*stringget_mcp_server_detailsGet full metadata for a specific MCP server by its reverse-DNS registry name (e.g. io.github.username/server-name). Returns all versions, remotes, packages, and tools.1 params
Get full metadata for a specific MCP server by its reverse-DNS registry name (e.g. io.github.username/server-name). Returns all versions, remotes, packages, and tools.
name*stringlist_mcp_serversBrowse all MCP servers in the registry with pagination. Use the next_cursor from the response to fetch subsequent pages.3 params
Browse all MCP servers in the registry with pagination. Use the next_cursor from the response to fetch subsequent pages.
cursorstringlatest_onlybooleanlimitintegerSponsors
Readme
MCP Registry Search
One connection. Access to every MCP server in the official MCP registry.
Endpoint: https://mcpregistrysearchwilfredleejr.vercel.app/api/mcp Transport: streamable-http Auth: None required Registry: io.github.Spacemandomains/mcp-registry-search
What it does
Gives any AI agent or LLM the ability to dynamically discover, search, and inspect every server in the official Model Context Protocol registry — at runtime, with no hardcoded tool knowledge.
Tools
- list_mcp_servers — paginate the full registry
- get_mcp_server_details — get full metadata for any server by reverse-DNS name
- search_mcp_registry — search servers by plain name or keyword
Connect
Add this endpoint to any MCP-compatible client:
https://mcpregistrysearchwilfredleejr.vercel.app/api/mcp
Use cases
- Agent-driven tool discovery
- Search by plain name instead of reverse-DNS
- Dynamic MCP server routing
- Registry monitoring and auditing
- Building meta-agents that orchestrate other MCP servers
Details
- Repository
- github.com/spacemandomains/mcp-registry-search
- Category
- Search & Web Crawling
- Transport
- HTTP
- Registry
- MCP registry, active
- Tools verified
- Nov 6, 2026