Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

MCPExplorer

by mcpexplorerversion 1.0.0i★ 1iRuns in the cloud
Registry nameio.github.mcpexplorer/mcpexplorer

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3Connect4
https://mcpexplorer.com/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3Connect4
https://mcpexplorer.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

Tool names and descriptions exactly as the server reported them on Nov 11, 2026. The maker wrote them, not us; we show them as plain text.

  • search_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.

  • get_server

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

  • get_capability

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

  • compare_servers

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

  • generate_runtime_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).

  • check_trust

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

  • get_alternatives

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

  • 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.

  • get_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.

  • 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.

  • 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.

  • 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.

  • plan_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

  • report_broken_server

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mcpexplorer, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 4 months ago

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 226 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 14 tool descriptions and found no hidden instructions to the AI

User reviews

No reviews yet

Compared with others in Search & AI memoryi

  • More stars than 73% of the other 5867 servers in this category
  • Published to the registry more recently than 20% of the other 5867 servers in this category
  • Basic checks equal to or better than 100% of the other 5867 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCPExplorer safe?

It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 4 months ago, and the latest version (1.0.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Ruflo, Context7, Metabase

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Ruflo

Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.

by ruvnetWidely used↓ 74.3K/wk★ 81.4KUpdated today

Runs on your computer

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 1.2M/wk★ 64.4KUpdated yesterday

Computer or cloud

Metabase

Lets AI clients search, explore, query, and visualize data in a Metabase instance.

by metabaseWidely used★ 50.3KUpdated 6 months ago

Runs in the cloud

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MCPExplorer

The search engine and trust layer for MCP servers.

→ mcpexplorer.com

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](https://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:

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):

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.