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

@modelcontextprotocol/inspector-cli

Skill Development Usable
Works inClaude Code
Usable Scanned — metadata only

Enables direct inspection and debugging of Model Context Protocol implementations, reducing integration friction and accelerating MCP server development cycl…

CLI for the Model Context Protocol inspector

10,442 starsSEE LICENSE IN LICENSEFreeQuick setup
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Enables direct inspection and debugging of Model Context Protocol implementations, reducing integration friction and accelerating MCP server development cycles for teams building Claude tooling.

Development teams building or maintaining MCP servers who need real-time protocol debugging and validation.

Claude Code Claude Cowork Claude Chat

https://www.npmjs.com/package/@modelcontextprotocol/inspecto...

By GitHub Actions

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
npx @modelcontextprotocol/inspector-cli

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me debug Claude integration issues by inspecting Model Context Protocol messages in real time
CostFree

Trust Signals Auto-scanned

Stars10,442Last updated2026-07-22LicenseSEE LICENSE IN LICENSEWeekly downloads214,002Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-23 · 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,442 GitHub stars; contributors unknown; last commit 1d ago; license SEE LICENSE IN 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
3/5
Security
3/5
Overall score3.15 / 5.00 UsableEvaluatedJul 2026
Scored from trust signals (evidence-eval-v1): 10,442 GitHub stars; contributors unknown; last commit 1d ago; license SEE LICENSE IN LICENSE.

← Back to the Claude Observatory

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

Start a conversation →