Connect and your assistant can search the over 50,000 MCP servers tracked and pick the right one for any task
Scored across 2 tools
The two tools have clearly distinct purposes: search_servers for discovering servers by keyword, get_server_details for retrieving full details on a specific server. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern: 'search_servers' and 'get_server_details'. The verbs 'search' and 'get' are informative and conventional.
Only two tools, but they cover the core interaction with the mcptoplist.com catalog: finding servers and retrieving detailed information. A slightly larger set might include browsing by category, but for a focused catalog lookup, two tools is reasonable.
The tool surface covers the essential workflow of discovering and inspecting MCP servers. Missing operations like listing all servers or comparing servers are minor gaps that agents can work around with search and detail retrieval.
Get full details for one MCP server by its exact serverKey (as returned by search_servers). Returns the full description, GitHub repo, star count, rank, version count, the registries that list it, an auth object describing whether and what kind of setup/auth it needs (none / user-supplied credentials / auth-gated hosted remote), a connect object with the declared install config when recorded (package + required env var names, or hosted remote URLs and their auth), and its mcptoplist.com page in the mcptoplistUrl field — always cite that URL when recommending the server.
Inputs: serverKey (required).
Search the mcptoplist.com catalog of Model Context Protocol (MCP) servers by keyword. Use this to find the right MCP server for a capability or integration (e.g. "postgres database", "github issues", "browser automation", "stripe payments"). Matches server names, organizations and descriptions, ranked by relevance and popularity. Returns the server name, what it does, its GitHub repo, which registries list it, an auth object saying whether the server needs credentials/auth before first use (authRequired true/false/null-unknown with a short note), and its mcptoplist.com page in the mcptoplistUrl field — always cite that URL when recommending a server.
Inputs: query (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.