Listing Criteria

Over 10,000 MCP servers are indexed across the web, many of them abandoned demos and one-off wrappers. This site has exactly one differentiator: quality over quantity. The rules are public — hold us to them.

Five hard rules

1. Active maintenance — commits, releases or official announcements within the last 90 days. The MCP ecosystem moves fast; an unmaintained server is a security liability, not an asset.
2. Trustworthy provenance — official/vendor-maintained first; community projects need 1,000+ GitHub stars or verifiable production adoption. Every card carries a provenance badge, no blurring.
3. One scenario, one pick — we recommend the single best option per job-to-be-done. No 'here are 20 similar ones' index-stuffing.
4. Works out of the box — public install paths only, no private invites or source edits. Every install command and remote endpoint on the cards has been checked.
5. Hand-reviewed — automated aggregation only surfaces candidates; every listing is manually checked for repo status, maintenance recency and positioning. The verification date is printed on each card.

Badge meanings

• Official / Vendor — maintained by the product owner itself. First priority.
• Official reference — Anthropic reference implementations. Note: educational examples by design; be careful with write operations in production.
• Community — high-star community-maintained implementations; review required credentials and permission scopes before use.
• remote — vendor-hosted HTTP endpoint; no local process, authorized via OAuth or token.

How risk levels are assigned

Every card carries a risk badge assigned by the rubric below; hover a badge for the entry-specific reasoning. Low risk doesn't mean install blindly — the real boundary is always the credential scope you grant.

• 🟢 Read-only (low) — reads information only, writes nothing: search, docs, design data, error monitoring, etc.
• 🟡 Writable (medium) — can create or modify content and data: repo PRs, task status, notes, database records. Start with a small scope.
• 🔴 High-risk — touches money, production infrastructure or cross-system automation: payments, cloud resources, clusters, orchestration. Least privilege + read-only first, always.

Security note

2025 ecosystem security research: ~88% of MCP servers require credentials, over half rely on long-lived static API keys, and only a minority use OAuth. When wiring servers to your agent: least privilege, read-only before write, pin versions (never bare npx -y in production), and keep active servers to 3–7.

Data sources & cadence

Candidates come from cross-referencing the official registry, major aggregators and high-quality roundups; stars and repo activity are verified live via the GitHub API (snapshot date in the footer). An automated patrol pipeline is planned — degraded entries get downgraded, degraded without a fix gets delisted.

Delisting log

Delisting isn't punishment — it's the site's core promise. A list is only worth trusting if it dares to delete.

• Gmail MCP Server (GongRzhe) — featured in several 2026 roundups; repo archived and unmaintained since Aug 2025. Delisted at the 2026-09-24 re-check.
• Slack / PostgreSQL / Puppeteer / Google Drive in the official references — moved by Anthropic into the archived repo; we now recommend vendor or community builds instead.
• DingTalk MCP — listed in the first CN batch; the repo went 451 days without updates (past the activity line) and the hosted plaza form couldn't be verified to our standard. Delisted 2026-09-25.

Submit a pick

Found a gem worth listing? Spotted an entry gone stale? Open an issue on the GitHub repo with the repo URL and your hands-on notes.