Is MCP Inspector safe?
MCP Inspector scores 71.5/100 (Grade B), ranked #91 of 417 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
71% of recent commits are signed;
last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
71.5/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
11.0/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-14
Newly Listed
First tracked at rank #90
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-15 01:30 UTC·Repo last pushed yesterday
MCP Inspector has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP Inspector publish package provenance?
Yes. MCP Inspector's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP Inspector have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MCP Inspector. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP Inspector actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Inspector use?
MCP Inspector ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Inspector's commits signed?
71% of the last 100 commits to MCP Inspector are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
MCP Server Support
high confidence
Implemented
MCP Inspector appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain MCP Inspector?
HVTrust scores MCP Inspector from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON
