BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

MCP Inspector

Workflow Setup & Config Solid
Works inClaude Code Claude Cowork Claude Chat
Solid Scanned — metadata only

Reduces time spent troubleshooting MCP connection failures by exposing schema mismatches and handshake errors before they cascade into production integration…

Debugging tool that inspects live MCP server tool schemas, parameters, and handshake details to fix connection issues in Claude Code.

10,473 starsFree

Reduces time spent troubleshooting MCP connection failures by exposing schema mismatches and handshake errors before they cascade into production integrations, lowering deployment risk.

Integration engineers and DevOps teams debugging MCP server configuration and Claude Code connectivity issues.

Claude Code Claude Cowork Claude Chat

https://github.com/modelcontextprotocol/inspector

How to Get It

This is a methodology or approach — no installation needed. See the Source link above for the full steps, or paste the source URL into Claude and ask it to summarise the recipe and help you apply it.

First thing to try

After installing, paste this into Claude:

Help me debug MCP server connection failures by inspecting live tool schemas and handshake details

Trust Signals Auto-scanned

Stars10,473Contributors139Last updated2026-07-25Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-25 · scanner v1

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 10,473 GitHub stars; 139 contributors; last commit 0d ago; license no license.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
2/5
Versatility
5/5
Reliability
5/5
Security
4/5
Overall score3.80 / 5.00 SolidEvaluatedJul 2026
Scored from trust signals (evidence-eval-v1): 10,473 GitHub stars; 139 contributors; last commit 0d ago; license no license.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →