Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
MCP adoption is broad enough that debugging the protocol is now part of normal developer workflow. Inspector is useful because it is official, current, package-installable through npx, and focused on the exact failure modes MCP builders hit: connection setup, capability negotiation, schema inputs, tool outputs, and logs. The main caution is that it intentionally runs or connects to MCP servers
Who should use it
Who should skip it
Skip modelcontextprotocol/inspector unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
modelcontextprotocol/inspector is tracked by RepoRadar as a code repository in the MCP tooling section. It was first seen on 2026-07-11 and last updated on 2026-07-11. The current verdict is 'try now' with a Gold tier and easy setup difficulty. modelcontextprotocol/inspector leads on workflow potential (9.5) and maturity (8.8); its lowest signal is evidence quality (7.2), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned modelcontextprotocol/inspector a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 100.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Inspector launches or connects to MCP servers and can send tool inputs; use known server commands and test credentials during debugging; The repository is in a license transition with Apache-2.0, MIT, and CC-BY-4.0 scopes; review the LICENSE file if embedding code or docs into another project.