Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
MCPExplorer MCP server exists for a simple reason — assistants are far more useful when they can act on MCPExplorer directly instead of describing what you should do. Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
MCPExplorer indexes Model Context Protocol servers and verifies each one with a live handshake — so you can see the real tools a server exposes, each labeled by risk, plus a trust score, before you install it.
Once MCPExplorer is connected, these are the calls the assistant has available:
llms.txt — ** https://mcpexplorer.com/llms.txtsearch_servers — Search the index by capability, transport, and riskget_server — A server's verified tools, install command, and trust breakdownget_capability — Servers that provide a given capabilitycompare_servers — Side-by-side comparison of two serversget_alternatives — Servers similar to a given onecheck_trust — Explainable trust score and reasoning for a servergenerate_runtime_config — Ready-to-paste client config for a serverlist_capabilities — The capability slugs you can search and look up bylist_runtimes — Runtimes generate_runtime_config supportsget_ecosystem_stats — Live totals + provenance/transport breakdownslist_loadouts — Curated server kits for a job (GTM, coding, research, …)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCPExplorer's toolset — llms.txt, search_servers, get_server and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mcpexplorer; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| llms.txt | ** <https://mcpexplorer.com/llms.txt> |
| search_servers | Search the index by capability, transport, and risk |
| get_server | A server's verified tools, install command, and trust breakdown |
| get_capability | Servers that provide a given capability |
| compare_servers | Side-by-side comparison of two servers |
| get_alternatives | Servers similar to a given one |
| check_trust | Explainable trust score and reasoning for a server |
| generate_runtime_config | Ready-to-paste client config for a server |
| list_capabilities | The capability slugs you can search and look up by |
| list_runtimes | Runtimes generate_runtime_config supports |
| get_ecosystem_stats | Live totals + provenance/transport breakdowns |
| list_loadouts | Curated server kits for a job (GTM, coding, research, …) |
| get_loadout | One kit with live trust + aggregated tool-risk |
| plan_toolset | Plain-language goal → a recommended governed toolset |
**Or add it to any MCP client:**
```json
{
"mcpServers": {
"mcpexplorer": {
"type": "streamable-http",
"url": "https://mcpexplorer.com/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.