MCPExplorer

io.github.mcpexplorerPublished by GitHub account mcpexplorerv1.0.0Updated Oct 25, 2026

Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A remote MCP server that lets an assistant search, vet, compare and assemble other MCP servers using verified tool lists, risk labels and trust scores.

What you can do
Search and browse the MCP server index, and look up capability slugs to filter by capability, transport or risk. Fetch a server's full record, compare two servers, find alternatives, and check its explainable trust score. Generate ready-to-paste client config for supported runtimes and list those runtimes. Explore curated loadouts and turn a plain-language goal into a recommended, governed toolset. View live ecosystem statistics and report a broken server listing for editorial review.
When to use it
Useful when choosing which MCP servers to add: checking what tools a server really exposes, whether its tools are read-only or destructive, and how trustworthy it is before installing. Also handy for assembling a set of servers for a specific job.
Requirements
A remote Streamable HTTP endpoint; no authentication, environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
Most tools only read the public index, but report_broken_server creates a submission for editorial review, so it writes data. Trust scores and verification come from a third party and should be treated as guidance, not a guarantee.

Installation

In SourceWeft

  1. Open MCPExplorer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcpexplorer%2Fmcpexplorer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcpexplorer": {
      "type": "http",
      "url": "https://mcpexplorer.com/mcp"
    }
  }
}

README

MCPExplorer

The search engine and trust layer for MCP servers.

→ mcpexplorer.com

[Website] [MCP Server]

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.

The problem

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:

  • what tools a server actually exposes,
  • whether those tools are read-only or can delete your data,
  • whether it needs credentials,
  • or whether it's still maintained —

until you install it and hope.

What MCPExplorer does

  • Verifies, doesn't just list. It runs the real MCP 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.
  • Labels tool risk. Every tool is tagged read / write / destructive, so you know what a server can do before you connect it.
  • Scores trust. A deterministic score from provenance, verification, adoption, and freshness — with every contributing factor shown on the page, not a black box.
  • Stays fresh. Every fact carries provenance and a "last checked" timestamp.

Currently ~1,000 servers indexed · 3,500+ tools extracted · 278 handshake-verified.

Start here

The MCPExplorer MCP server

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:

bash
claude mcp add --transport http mcpexplorer https://mcpexplorer.com/mcp

Or add it to any MCP client:

json
{  "mcpServers": {    "mcpexplorer": {      "type": "streamable-http",      "url": "https://mcpexplorer.com/mcp"    }  }}

Tools (14):

ToolWhat it does
search_serversSearch the index by capability, transport, and risk
get_serverA server's verified tools, install command, and trust breakdown
get_capabilityServers that provide a given capability
compare_serversSide-by-side comparison of two servers
get_alternativesServers similar to a given one
check_trustExplainable trust score and reasoning for a server
generate_runtime_configReady-to-paste client config for a server
list_capabilitiesThe capability slugs you can search and look up by
list_runtimesRuntimes generate_runtime_config supports
get_ecosystem_statsLive totals + provenance/transport breakdowns
list_loadoutsCurated server kits for a job (GTM, coding, research, …)
get_loadoutOne kit with live trust + aggregated tool-risk
plan_toolsetPlain-language goal → a recommended governed toolset
report_broken_serverFlag a stale or broken listing

How verification works

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.

For agents & programmatic access

Submit a server

Missing something? Submit it at https://mcpexplorer.com/submit — it enters the same verification pipeline as everything else.

FAQ

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.

Source: README.md at commit 2cd6e96

Tools

14

search_servers

Search MCP servers

Search the MCPExplorer index of MCP servers by free text and filters. Omit `query` to browse the whole index ranked by trust score. Every filter either applies or is echoed back in `ignored_filters` with a reason — filters never silently do nothing.

Parameterslimitquerytransportcapabilityrisk_levelofficial_status

get_server

Get an MCP server

Fetch the full record for one MCP server by slug: install methods, tools, trust, verification, and provenance.

Parametersslugrequired

get_capability

Get a capability

List the best MCP servers that provide a capability (e.g. 'send-email', 'web-search'), ranked by trust.

Parametersslugrequired

compare_servers

Compare two MCP servers

Compare two MCP servers side by side: trust, transport, tools, install, and links.

Parametersarequiredbrequired

generate_runtime_config

Generate MCP setup config

Generate the install + client config for an MCP server in a given runtime (claude-desktop, cursor, vscode, windsurf, cline, continue, goose, openai-agents, langgraph, crewai).

Parametersslugrequiredruntimerequired

check_trust

Check trust

Return the explainable trust score, label, scoring reasons, and verification history for an MCP server.

Parametersslugrequired

get_alternatives

Get alternatives

Find verified MCP servers with the same capabilities as a given server, ranked by trust.

Parametersslugrequired

list_loadouts

List loadouts

List curated loadouts — deliberately-assembled kits of MCP servers + governance + plays for a specific job (GTM, coding, research, support, infra). The agent-facing version of the /loadouts product. Use get_loadout for the full kit with live trust.

Takes no parameters.

get_loadout

Get a loadout

Fetch one curated loadout: its servers (each with role + LIVE trust/transport/tool-risk from the index), an aggregated governance posture for the whole kit, and the plays (see→decide→act sequences) it's designed to run.

Parametersslugrequired

list_capabilities

List capabilities

List the capability slugs an agent can filter or look up by (e.g. 'send-email', 'query-database'), most-populated first. Use these with get_capability or search_servers' capability filter — the taxonomy isn't guessable.

Parameterslimit

get_ecosystem_stats

Get ecosystem stats

Live snapshot of the indexed MCP ecosystem: totals (servers, tools, handshake-verified), provenance and transport breakdowns, and the current top-trust / most-adopted / newest / biggest-trust-riser servers.

Takes no parameters.

list_runtimes

List runtimes

List the runtimes generate_runtime_config supports (Claude Desktop, Cursor, VS Code, agent frameworks, …), with each one's config path. Enumerate these instead of guessing runtime slugs.

Takes no parameters.

plan_toolset

Plan a governed toolset

Turn a plain-language goal into a recommended, governed toolset: the best-fit curated loadout (matched transparently by goal terms) plus an assembled set of the most relevant indexed servers, each with LIVE trust and tool-risk, and an aggregate governance posture for the kit. The decision layer over search/capability/trust/loadouts.

Parametersgoalrequiredlimitrisk_tolerance

report_broken_server

Report a broken server

Report that an MCP server's install, docs, or endpoint is broken. Creates a submission for editorial review.

Parametersslugrequireddetailrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts