MCP servers live across multiple registries and directories. Lists go stale, names collide, and a listing is not a safety review. This guide shows where to look, what to check, and how to let an AI agent search and install with MCPfinder.
There is no single complete catalog. Most developers combine a few sources:
For how each directory accepts new servers, see MCP server directories compared.
MCPfinder aggregates the Official MCP Registry and Glama into one index your agent can query — it works with those sources, not as a replacement for your AI client.
MCP server discovery happens at two levels:
In both cases a search result is only a candidate. Check the publisher, tools, required secrets, and transport before you install, using the checklist below.
Search by the job (filesystem, GitHub, Slack, Postgres), not by vanity rankings. Wrong tools waste context and increase risk.
Prefer clear upstream repos, multi-source listings, recent updates, and low warning-flag counts. A popular listing can still be abandoned.
Read required environment variables and OAuth scopes. Prefer least privilege; treat account-wide keys as root for that service.
Confirm transport and config shape for Claude Desktop, Cursor, Claude Code, Cline, Windsurf, or your IDE. Install JSON differs by client.
A registry entry shows that someone published a server, not that its endpoint answers right now. mcpreflight’s weekly read-only scan of the Official MCP Registry (published 19 October 2026) found that 4,783 of 9,991 remote endpoints (47.9%) completed a clean anonymous handshake, 3,171 answered with an authentication challenge (HTTP 401), 1,984 gave no anonymous response, and 53 failed.
For a remote server that requires sign-in, a 401 asking for authentication is normal; no anonymous response is a reason to check the repository before you install. MCPfinder’s trust signals and warning flags come from registry metadata plus npm and GitHub checks (such as source count, repository, recency, deprecated packages and archived repos), not from a live connection test of the server.
Call search_mcp_servers with a capability or keyword. Review scores and recommendation reasons across registries.
get_server_details surfaces tools, env vars, warnings, and transport before you commit.
get_install_config emits paste-ready JSON for your client. Restart and verify the tools load.
# Run MCPfinder via npx, then ask your agent to search $ npx -y @mcpfinder/server # Example ask: "find MCP servers for sqlite and show warnings"
Install MCPfinder once. Search the Official MCP Registry and Glama, inspect warnings, and paste client-ready config.