Is mcp-proxy safe to use?

mcp-proxy has an HVTrust score of 79.7/100 (Grade B), ranked #70 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for mcp-proxy?

mcp-proxy scores 79.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.7k GitHub stars and is categorized under Protocols & Tool Integration.

mcp-proxy

sparfenyuk/mcp-proxy

A bridge between Streamable HTTP and stdio MCP transports

Protocols & Tool Integration Python Grade B Listed MIT

79.7/100

Rank #70 of 1283

Compare mcp-proxy

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-07-20 · 22d ago

Recent change

Grade Changed

Is mcp-proxy safe? mcp-proxy scores 79.7/100 (Grade B), ranked #70 of 1283 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 5.7/10; 50% of recent commits are signed; last pushed 2026-07-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#3 FastMCP (TypeScript) — 86.5 (A) → #4 MCP Apps — 85.7 (A) → #6 CLI-Anything — 79.3 (B) → #7 Composio — 75.8 (B) →

Quick Trust Read

What Would Improve It

Improve maintenance to lift the weakest part of the trust profile.

Recent Changes

2026-08-08

Grade Changed

Trust grade A → B

2026-07-28

Grade Changed

Trust grade C → A

2026-07-28

Rank Moved

Rank rose 233 spots (#290 → #57)

Maintainer Checklist

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

Compare with MCP Inspector Get email alerts for mcp-proxy View Protocols & Tool Integration Report missing data

53.9

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 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 →

Activity & Reach

Stars

2.7k

Forks

254

Last Push

2026-07-20

22 days ago

Commits (4 wk)

Downloads (7d)

437,913

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #68

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

79.7 / 100 · 100.0% confidence

mcp-proxy Protocols & Tool Integration average (57 agents)

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

17.1 / 25

8.5 above avg 8.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.9 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

10.5 / 20

3.3 below avg 13.8

AdoptionLog-scaled stars · package downloads

15.8 / 20

5.4 above avg 10.4

Activity Inputs

53.9 / 100

StarsRepository reach

20.6 / 30

FreshnessLast push recency

21.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

50%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 4

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 7

Packaging 10

Pinned-Dependencies 8

SAST 8

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is mcp-proxy safe?

Public supply-chain signals for mcp-proxy are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but mcp-proxy carries less obvious unverified-evidence risk than projects with thin signals.

Does mcp-proxy publish package provenance?

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

Does mcp-proxy have an OpenSSF Scorecard?

mcp-proxy has an OpenSSF Scorecard score of 5.7/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-proxy actively maintained?

Maintained. Last push was 22 days ago.

What license does mcp-proxy use?

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

Are mcp-proxy's commits signed?

50% of the last 100 commits to mcp-proxy 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-proxy head-to-head

mcp-proxy vs MCP Inspector → mcp-proxy vs A2A / Agent2Agent Protocol → mcp-proxy vs FastMCP (TypeScript) →

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-proxy 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-proxy?

For maintainers

HVTrust scores mcp-proxy 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-08-08

Grade Changed

Trust grade A → B

2026-07-28

Grade Changed

Trust grade C → A

2026-07-28

Rank Moved

Rank rose 233 spots (#290 → #57)

2026-07-28

HVTrust Changed

HVTrust up 29.6pts (51.7 → 81.3)

2026-07-20

Activity Score Changed

Activity score up 6pts (51 → 57)

2026-07-15

Scorecard Added

OSSF Scorecard: 5.9/10

2026-07-15

Grade Changed

Trust grade D → C

2026-07-15

Rank Moved

Rank rose 27 spots (#325 → #298)

2026-07-15

HVTrust Changed

HVTrust up 8.2pts (42.2 → 50.4)

2026-07-14

Newly Listed

First tracked at rank #325

GitHub → PyPI: mcp-proxy

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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