GUIDE · MCP DISCOVERY

How to find MCP servers that fit your client

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.

Registries and directories people actually use

There is no single complete catalog. Most developers combine a few sources:

  • Official MCP Registry — vendor-neutral metadata for publicly published servers; best starting point for “who published this?”
  • Glama — large searchable index with deeper per-server metadata and inspection tooling
  • Smithery — public directory, now powered by Arcade.dev; Smithery said its hosted MCP proxy, API and server URLs would stop working on 31 October 2026 (announcement), so use each vendor’s own MCP URL instead (how to switch)
  • Directory sites (for example mcp.so) — useful for browsing categories; still verify before you connect

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.

How MCP server discovery works

MCP server discovery happens at two levels:

  • Human discovery: you browse registries and directory sites, compare candidates, then paste a config into your client.
  • Agent discovery: your assistant searches for a missing capability while it works. The Official MCP Registry exposes a public REST API that tools and aggregators can query, and an MCP server such as MCPfinder can search the Official Registry and Glama from inside your client.

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.

What to check before you install

Capability fit

Search by the job (filesystem, GitHub, Slack, Postgres), not by vanity rankings. Wrong tools waste context and increase risk.

Trust signals

Prefer clear upstream repos, multi-source listings, recent updates, and low warning-flag counts. A popular listing can still be abandoned.

Secrets & scope

Read required environment variables and OAuth scopes. Prefer least privilege; treat account-wide keys as root for that service.

Client compatibility

Confirm transport and config shape for Claude Desktop, Cursor, Claude Code, Cline, Windsurf, or your IDE. Install JSON differs by client.

Listed is not the same as responding

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.

Let your assistant search, then install

01

Search

Call search_mcp_servers with a capability or keyword. Review scores and recommendation reasons across registries.

02

Inspect

get_server_details surfaces tools, env vars, warnings, and transport before you commit.

03

Install

get_install_config emits paste-ready JSON for your client. Restart and verify the tools load.

Quick start · any MCP clientEXAMPLE
# Run MCPfinder via npx, then ask your agent to search
$ npx -y @mcpfinder/server

# Example ask: "find MCP servers for sqlite and show warnings"

Common questions

How do I find MCP servers?
Start with the Official MCP Registry for publisher identity, then search a broader index such as Glama. For agent-driven discovery, install MCPfinder so your AI client can search those registries, inspect trust signals, and generate install JSON.
What is MCP server discovery?
MCP server discovery is finding a Model Context Protocol server that provides the tools you need, checking who publishes it and what access it requires, and getting the right config for your client. People browse registries and directories; agents can use a discovery server such as MCPfinder, which searches registry data for them.
Which MCP registries should I check?
The Official MCP Registry is the vendor-neutral metadata source. Glama is a widely used downstream directory with a much larger index. Smithery remains a public directory (now powered by Arcade.dev), but it announced that its hosted proxy and server URLs would stop working on 31 October 2026. Directory sites such as mcp.so are useful for browsing. MCPfinder aggregates the Official Registry and Glama into one agent-searchable index.
Is a listing the same as a safe install?
No. A directory listing is not a security review. Inspect tools, required environment variables, warnings, transport, and the upstream repository before connecting a server to an AI client.
How is MCPfinder different from a directory website?
MCPfinder is primarily an MCP server your assistant calls. It searches registries, surfaces trust signals and warnings, and emits client-specific install config. The mcpfinder.dev site explains the workflow; the product experience is agent-native discovery.

Related MCP finder pages

Find MCP servers from your agent

Install MCPfinder once. Search the Official MCP Registry and Glama, inspect warnings, and paste client-ready config.