I’ve been building agent-lsp , an MCP server that gives Claude Code access to real language servers (gopls, pyright, rust-analyzer, etc.). One of its skills is /lsp-inspect, a code quality audit that uses LSP batch analysis and heuristic checks to find bugs. I pointed it at Anthropic’s own MCP Python SDK (23K stars) to see what it would find. It surfaced 24 issues. 14 were exception chaining bugs: raise ValueError(str(e)) without from e, which discards the original traceback and makes debugging impossible for downstream callers. Filed two PRs. Both merged within 24 hours. #2542: 2 broken exception chains in get_prompt and read_resource (merged) #2565: 12 remaining sites across 7 files The inspector didn’t use an LLM to guess at code quality. It used get_change_impact to batch-analyze every exported symbol, then source-level pattern matching for error handling gaps. Structured analysis, not vibes. This isn’t the first time. agent-lsp has found and fixed bugs across the MCP ecosystem: MCP Go SDK (Anthropic): HTTP response body leak. Merged. MCP PHP SDK (Anthropic): URI regex rejects valid RFC 3986 URIs. Merged. mcp-go (community SDK): 5 PRs merged. Top 10 all-time contributor. 17 merged PRs across 22 organizations total. If you’re using Claude Code and want your agent to have type-aware navigation, blast-radius analysis, and speculative editing (preview changes in memory before writing to disk), agent-lsp adds all of that as a single MCP server: claude mcp add agent-lsp – agent-lsp agent-lsp ships 21 skills that enforce correct tool sequencing. Instead of hoping your agent checks references before renaming or runs diagnostics after editing, skills like /lsp-refactor and /lsp-safe-edit make those steps mandatory. The agent calls one skill; the skill handles the multi-step workflow internally. https://github.com/blackwell-systems/agent-lsp submitted by /u/blackwell-systems
Originally posted by u/blackwell-systems on r/ClaudeCode