You install a popular MCP server, it breaks, and then you find out the repo was archived months ago. Most “top MCP servers” lists are just GitHub star counts copy-pasted into a listicle. That’s a bad filter. A popular Obsidian MCP project (jacksteamdev/obsidian-mcp-tools, 800+ stars) is now archived — read-only, no more fixes. Mem0’s own self-hosted MCP server (mem0ai/mem0-mcp) is archived — the README opens with a notice that it’s no longer maintained, and Mem0 now points users to its cloud-hosted server instead. Stars measure past hype, not whether a project still works.
We checked five servers instead of just ranking them: recent commit activity, how open issues get handled, and whether the practical claim (“free search,” “read-only by default”) actually holds up in the current version. These five passed.
What the full guide covers:
- What You’ll Need
- The Five, One at a Time
- Verify Each One Actually Works
The commands, our own test notes, and the troubleshooting steps are in the full guide, which we keep up to date:
Top comments (1)
One more check worth adding to a maintenance pass: whether the package on npm was built from the repository by CI.
npm view <package> --jsonshowsdist.attestationswith an SLSA provenance statement when it was, andnpm audit signaturesverifies it. An MCP server runs with whatever access your client gives it, so knowing the published code matches a public commit matters more than the star count.