NaNMesh MCP checks GitHub issues before Claude recommends libraries

What it does

NaNMesh MCP addresses the problem where Claude recommends libraries based on outdated training data. The creator integrated Clerk for authentication based on Claude's recommendation, then hit a bug where JWT token refresh silently fails with Supabase RLS. The fix took 6 hours, and the bug had 17 comments on GitHub that Claude couldn't see.

How it works

The MCP server tracks 57 products by crawling GitHub Issues, Stack Overflow, and Reddit for real problems affecting development tools. When Claude recommends something, it can check known bugs first.

For example: ask Claude "should I use Clerk or Auth0?" Claude calls nanmesh.entity.search, sees that Clerk has 5 open issues including the JWT/Supabase bug, and Auth0 has an Edge Runtime compatibility problem.

Installation and features

Install with one line in your Claude config:

"nanmesh-mcp": { "command": "npx", "args": ["-y", "nanmesh-mcp"] }

The MCP provides 34 tools total. You can search products, check known issues, compare trust scores, and report whether a recommendation worked.

Data improvement

The data gets better as more agents use it. If Claude recommends Stripe and it works, you can report that outcome. If it breaks, report that too. Over time the trust scores reflect real usage, not marketing copy.

The MCP is open source with a free API. No account is needed to search. Agent registration (30 seconds, also free) lets you leave reviews that carry more weight.