updated 2026-10-13 08:09 UTC

MCP Inspector

Repository Website by modelcontextprotocol

Visual testing tool for MCP servers

Protocols & Tool Integration TypeScript Listed NOASSERTION

Is MCP Inspector safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.3 / 10
Provenance Attested
Signed commits 32%
Last push today
Advisories None known
Compare MCP Inspector

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Inspector scores 91.7/100 (Grade A), ranked #11 of 1371 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; OSSF Scorecard rates its supply-chain practices 7.3/10; 32% of recent commits are signed; no published advisory affects its latest release (@modelcontextprotocol/inspector); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Inspector could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Inspector and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/modelcontextprotocol/inspector, NOASSERTION, last pushed 2026-10-13. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.3/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 4
    SAST 2
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @modelcontextprotocol/inspector 2.10.1. No published advisory affects it (OSV, checked 2026-10-13).

Changes to this chain

  • 2026-09-23 License classification changed from unlicensed to open
  • 2026-07-29 License classification changed from open to unlicensed

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Inspector’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Inspector compares in Protocols & Tool Integration

  1. #1 MCP TypeScript SDK 94.6 +2.9
  2. #2 MCP Python SDK 93.9 +2.2
  3. #3 MCP Inspector 91.7 this agent
  4. #4 A2A / Agent2Agent Protocol 89.4 −2.3
  5. #5 FastMCP (TypeScript) 86.8 −4.9

Bars show each HVTrust score; the tick marks MCP Inspector’s 91.7.

Where the 91.7 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

91.7 / 100 · 100.0% confidence

MCP Inspector Protocols & Tool Integration average (62 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.2 / 25
7.3 above avg 10.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.2 above avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
14.7 / 17
1.7 above avg 13.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
17.2 / 20
6.1 above avg 11.1

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
License Changed
License classification changed from unlicensed to open
2026-09-23
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-23
Rank Moved
Rank rose 45 spots (#65 → #20)
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with MCP TypeScript SDK Get email alerts for MCP Inspector View Protocols & Tool Integration Report missing data
89.1
Activity sub-score · out of 100
#3
In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 refreshed 2026-10-13 08:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
11.1k
Forks
1.5k
Last Push
2026-10-13
today
Commits (4 wk)
691
Downloads (7d)
399,346
npm
HN mentions (30d)
—
Open Issues
24
Rank Change
=
was #11

Analysis

Activity Inputs

89.1 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.8 / 20

Common questions about MCP Inspector

Public supply-chain signals for MCP Inspector are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but MCP Inspector carries less obvious unverified-evidence risk than projects with thin signals.
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?
MCP Inspector has an OpenSSF Scorecard score of 7.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
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?
32% 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.

Compare MCP Inspector head-to-head

MCP Inspector vs MCP TypeScript SDK → MCP Inspector vs MCP Python SDK → MCP Inspector vs A2A / Agent2Agent Protocol →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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
None detected
No clear plugin system or broad tool surface detected.
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?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 6HVTrust 3Score 2License 2Grade 2Warning Issued 1Warning Cleared 1
2026-09-23
License Changed
License classification changed from unlicensed to open
2026-09-23
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-23
Rank Moved
Rank rose 45 spots (#65 → #20)
2026-09-23
HVTrust Changed
HVTrust up 7.0pts (82.6 → 89.6)
2026-09-21
Rank Moved
Rank rose 46 spots (#111 → #65)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 606 spots (#699 → #93)
2026-09-05
HVTrust Changed
HVTrust up 29.8pts (52.8 → 82.6)
2026-09-04
Rank Moved
Rank dropped 20 spots (#679 → #699)
2026-09-03
Warning Issued
Warning: eligibility issues detected
2026-09-03
Grade Changed
Trust grade A → C
2026-09-03
Rank Moved
Rank dropped 669 spots (#10 → #679)
2026-09-03
HVTrust Changed
HVTrust down 37.9pts (90.7 → 52.8)
2026-07-29
License Changed
License classification changed from open to unlicensed
2026-07-28
Activity Score Changed
Activity score up 12pts (77 → 89)
2026-07-18
Rank Moved
Rank rose 17 spots (#28 → #11)
2026-07-18
Activity Score Changed
Activity score up 9pts (68 → 77)
GitHub → Website → npm: @modelcontextprotocol/inspector

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 91.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-inspector.svg)](https://hvtracker.net/agents/mcp-inspector)
HTML:
<a href="https://hvtracker.net/agents/mcp-inspector"><img src="https://hvtracker.net/badge/mcp-inspector.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON