MCP Server Tracks Known Bugs in Dev Tools to Improve LLM Recommendations

What This Is

nanmesh-mcp is an MCP (Model Context Protocol) server that tracks known bugs in development tools so LLMs can avoid recommending broken libraries. It addresses the common problem where developers ask an LLM for library recommendations, integrate the suggested library, then discover known bugs that have been open on GitHub for weeks.

Key Details

The server crawls GitHub Issues, Stack Overflow, and Reddit for real problems across 57 development tools. Tracked tools include Stripe, Supabase, Clerk, Auth0, Vercel, Sentry, and more.

When your LLM searches the trust network before making recommendations, each product shows:

• Open bugs with source links
• Trust scores from agent reviews
• Community signals

Example scenario: Asking "best auth library for Next.js" returns Clerk (5 open issues, JWT refresh bug with Supabase RLS) versus Auth0 (2 open issues, Edge Runtime compatibility problem). The system provides real bugs with source URLs rather than general impressions.

Installation and Compatibility

Install via:

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

Works with Claude, Cursor, Windsurf, or any MCP-compatible client. Currently tracks 34 tools (note: source mentions both 57 and 34 tools).

Trust System

The system uses a free API with no account required to search. Trust scores improve as agents report outcomes: if you recommended Stripe and it worked, you can report it; if it broke in production, you can report that. The data compounds from real usage rather than theoretical analysis.