Server data from the Official MCP Registry
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Remote endpoints: streamable-http: https://mcpexplorer.com/mcp
MCPExplorer is a documentation and manifest repository for an MCP server index/search product. The README describes the MCPExplorer MCP server itself, which exposes 14 read-only search and lookup tools over HTTP without authentication. No source code for the actual server implementation was provided for analysis, so this assessment is based on the documented interface and stated architecture. The server's design is appropriate for its purpose: it provides search, verification, and trust-scoring capabilities with no write operations, no credential handling, and reasonable permission scope for a developer tool.
1 file analyzed · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
The search engine and trust layer for MCP servers.
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.
Every "awesome MCP" list is a static, unverified README. MCPExplorer actually runs the servers.
This repo is the public home for MCPExplorer's docs and its MCP server manifest. The product itself lives at mcpexplorer.com.
As the MCP ecosystem grew past thousands of servers, the lists stopped being useful. From a name and a one-line description you can't tell:
until you install it and hope.
tools/list handshake on
every server — remote servers over the network, local/stdio servers in a
hardened, ephemeral Docker sandbox — and extracts the true tool surface.Currently ~1,000 servers indexed · 3,500+ tools extracted · 278 handshake-verified.
MCPExplorer exposes its own MCP server, so you can search, vet, and assemble
servers from inside your agent — without leaving your client. Hand plan_toolset
a plain-language goal and get back a recommended, governed toolset.
Endpoint: https://mcpexplorer.com/mcp (Streamable HTTP, no auth)
Add it to Claude Code:
claude mcp add --transport http mcpexplorer https://mcpexplorer.com/mcp
Or add it to any MCP client:
{
"mcpServers": {
"mcpexplorer": {
"type": "streamable-http",
"url": "https://mcpexplorer.com/mcp"
}
}
}
Tools (14):
| Tool | What it does |
|---|---|
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 |
report_broken_server | Flag a stale or broken listing |
Every server flows through a crawler pipeline:
discover → fetch → parse → normalize → resolve → enrich →
classify → verify (live handshake) → score trust → decide indexability
The verify stage is the heart of it. Remote servers are probed over the
network; local/stdio servers are executed in a locked-down container
(--read-only, --cap-drop ALL, --security-opt no-new-privileges, no host
mounts, no secrets, memory/CPU/PID limits, auto-removed) that runs only known
launchers (npx/uvx/uv/pnpm/bunx). The handshake extracts the real
tools/list, and each tool's risk is derived from its name and schema.
A page is only indexed once it has real MCP-server evidence and enough verified facts — so the index stays servers, not framework repos or link lists.
https://mcpexplorer.com/mcp (see above)Missing something? Submit it at https://mcpexplorer.com/submit — it enters the same verification pipeline as everything else.
Is this affiliated with Anthropic? No. MCP is Anthropic's open protocol; MCPExplorer is an independent index built on top of it.
Is the trust score a black box?
No. It's deterministic, and every +/− factor is shown on each server's page.
How do you run untrusted servers safely? Local/stdio servers only ever run inside the hardened, ephemeral container described above — never on the host, never with secrets.
MCPExplorer · mcpexplorer.com · a discovery, trust, and capability graph for MCP servers.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.