Is Metro MCP safe to use?

Metro MCP has an HVTrust score of 66.5/100 (Grade B), ranked #464 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Metro MCP?

Metro MCP scores 66.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 85 GitHub stars and is categorized under MCP Servers.

Metro MCP

Repository Website

🚇 A plugin-based MCP server for React Native runtime debugging, inspection, and automation. Connects to Metro bundler via Chrome DevTools Protocol — no app code changes needed for most features.

MCP Servers TypeScript Listed MIT

Is Metro MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance Attested

Signed commits 0%

Last push 43d ago

Advisories None known

Compare Metro MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Metro MCP scores 66.5/100 (Grade B), ranked #464 of 1378 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 4.3/10; recent commits are unsigned; no published advisory affects its latest release (metro-mcp); last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Metro MCP 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.

Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +9.8 → 76.3 B · #126 of 781
Sign every commit0% signed today +5.0 → 71.5 B · #196 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Metro MCP 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.

Source Unsigned

github.com/steve228uk/metro-mcp, MIT, last pushed 2026-09-04. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0
Published packages Linked and attested
- npm metro-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: metro-mcp 0.15.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-29 OSSF Scorecard: 4.4/10

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 Metro MCP’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 Metro MCP compares in MCP Servers

#268 Laravel Boost 66.5 ±0
#269 Umbraco CMS MCP Dev 66.5 ±0
#270 Metro MCP 66.5 this agent
#271 Gnosis MCP 66.5 ±0
#272 MCP Server for WinDbg Crash Analysis 66.4 −0.1

Bars show each HVTrust score; the tick marks Metro MCP’s 66.5.

Where the 66.5 comes from

HVTrust dimensions vs the MCP Servers average

66.5 / 100 · 100.0% confidence

Metro MCP MCP Servers average (781 agents)

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

12.9 / 25

2.4 above avg 10.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.5 above avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

9.1 / 20

3.2 below avg 12.3

AdoptionLog-scaled stars · package downloads

8.6 / 20

1.2 above avg 7.4

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 14 spots (#425 → #439)

2026-10-05

Rank Moved

Rank dropped 56 spots (#355 → #411)

2026-10-05

Activity Score Changed

Activity score down 6pts (43 → 36)

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 43 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Metro MCP View MCP Servers Report missing data

35.0

Activity sub-score · out of 100

#270

In MCP Servers

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 →

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars

Forks

Last Push

2026-09-04

43 days ago

Commits (4 wk)

Downloads (7d)

896

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #458

Analysis

Activity Inputs

35.0 / 100

StarsRepository reach

11.6 / 30

FreshnessLast push recency

19.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.2 / 20

Common questions about Metro MCP

Metro MCP 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 Metro MCP publish package provenance?

Yes. Metro MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Metro MCP have an OpenSSF Scorecard?

Metro MCP has an OpenSSF Scorecard score of 4.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 Metro MCP actively maintained?

Slowing down. Last push was 43 days ago — keep an eye on whether activity resumes.

What license does Metro MCP use?

Metro MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Metro MCP's commits signed?

0% of the last 100 commits to Metro MCP 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.

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

Metro MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

How this surface has changed

Detected changes to Metro MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Metro MCP?

For maintainers

HVTrust scores Metro MCP 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-10-09

Rank Moved

Rank dropped 14 spots (#425 → #439)

2026-10-05

Rank Moved

Rank dropped 56 spots (#355 → #411)

2026-10-05

Activity Score Changed

Activity score down 6pts (43 → 36)

2026-10-04

Rank Moved

Rank dropped 130 spots (#225 → #355)

2026-10-04

HVTrust Changed

HVTrust down 6.1pts (75.3 → 69.2)

2026-10-04

Activity Score Changed

Activity score down 19pts (62 → 43)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Rank Moved

Rank dropped 13 spots (#205 → #218)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 588 spots (#793 → #205)

2026-09-23

HVTrust Changed

HVTrust up 47.0pts (28.9 → 75.9)

2026-09-22

Newly Listed

First tracked at rank #793

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 11 spots (#196 → #207)

2026-09-06

Rank Moved

Rank dropped 25 spots (#137 → #162)

2026-09-05

Rank Moved

Rank dropped 33 spots (#104 → #137)

2026-09-04

Grade Changed

Trust grade C → B

2026-09-04

Rank Moved

Rank rose 624 spots (#728 → #104)

2026-09-04

HVTrust Changed

HVTrust up 28.2pts (51.0 → 79.2)

2026-09-04

Activity Score Changed

Activity score up 5pts (60 → 66)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 31 spots (#759 → #728)

2026-09-03

Activity Score Changed

Activity score up 12pts (48 → 60)

2026-09-02

Activity Score Changed

Activity score up 11pts (37 → 48)

2026-09-01

Rank Moved

Rank dropped 31 spots (#734 → #765)

2026-08-31

Rank Moved

Rank dropped 33 spots (#701 → #734)

2026-08-30

Rank Moved

Rank dropped 23 spots (#678 → #701)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.4/10

2026-08-29

Rank Moved

Rank rose 97 spots (#775 → #678)

2026-08-29

HVTrust Changed

HVTrust up 6.1pts (40.3 → 46.4)

2026-08-28

Rank Moved

Rank dropped 41 spots (#734 → #775)

2026-08-28

Activity Score Changed

Activity score down 6pts (44 → 38)

2026-08-27

Rank Moved

Rank dropped 22 spots (#712 → #734)

2026-08-26

Rank Moved

Rank dropped 97 spots (#615 → #712)

2026-08-16

Rank Moved

Rank dropped 14 spots (#594 → #608)

2026-08-10

Rank Moved

Rank dropped 24 spots (#564 → #588)

2026-08-08

Newly Listed

First tracked at rank #566

GitHub → Website → npm: metro-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

Metro MCP

How Metro MCP could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Metro MCP compares in MCP Servers

Where the 66.5 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Metro MCP

AI agent surface

Maintain Metro MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers