Is MCP Inspector safe to use?

MCP Inspector has an HVTrust score of 90.0/100 (Grade A), ranked #11 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Inspector?

MCP Inspector scores 90.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 10.7k GitHub stars and is categorized under Protocols & Tool Integration.

MCP Inspector

modelcontextprotocol/inspector

Visual testing tool for MCP servers

Protocols & Tool Integration TypeScript Grade A Listed NOASSERTION Unlicensed

90.0/100

Rank #11 of 1308

Compare MCP Inspector

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

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-19 · 0d ago

Recent change

No recent signal change

Is MCP Inspector safe? MCP Inspector scores 90.0/100 (Grade A), ranked #11 of 1308 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 6.1/10; 71% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#2 A2A / Agent2Agent Protocol — 89.5 (A) → #3 FastMCP (TypeScript) — 86.6 (A) → #4 MCP Apps — 85.9 (A) → #5 CLI-Anything — 79.8 (B) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-07-29

License Changed

License classification changed from open to unlicensed

2026-07-28

Activity Score Changed

Activity score up 12pts (77 → 89)

Maintainer Checklist

Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.

Raise Scorecard signals Current OSSF Scorecard is 6.1/10. Tighten the weakest checks to improve public safety evidence.

Compare with A2A / Agent2Agent Protocol Get email alerts for MCP Inspector View Protocols & Tool Integration Report missing data

89.0

Activity sub-score · out of 100

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

10.7k

Forks

1.5k

Last Push

2026-08-19

today

Commits (4 wk)

193

Downloads (7d)

185,338

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #11

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

90.0 / 100 · 100.0% confidence

MCP Inspector Protocols & Tool Integration average (58 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.7 / 25

10.2 above avg 8.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.7 / 17

2.3 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

6.1 above avg 13.9

AdoptionLog-scaled stars · package downloads

16.7 / 20

6.4 above avg 10.3

Activity Inputs

89.0 / 100

StarsRepository reach

24.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.1 / 10

OpenSSF Scorecard · scanned Aug 15, 2026

Signed Commits

71%

of last 100 commits verified

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 0

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 1

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Is MCP Inspector safe?

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 6.1/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?

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.

Compare MCP Inspector head-to-head

MCP Inspector vs A2A / Agent2Agent Protocol → MCP Inspector vs FastMCP (TypeScript) → MCP Inspector vs MCP Apps →

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

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

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)

2026-07-15

Scorecard Added

OSSF Scorecard: 6.6/10

2026-07-15

Grade Changed

Trust grade B → A

2026-07-15

Rank Moved

Rank rose 56 spots (#90 → #34)

2026-07-15

HVTrust Changed

HVTrust up 13.9pts (71.6 → 85.5)

2026-07-14

Newly Listed

First tracked at rank #90

GitHub → npm: @modelcontextprotocol/inspector

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON