Is mcp-proxy safe?
mcp-proxy scores 42.1/100 (Grade D), ranked #325 of 417 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
50% of recent commits are signed;
last pushed 2026-06-08. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
42.1/100 · Grade D
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
10.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 #325
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Refresh maintenance signalsThe repo was last pushed 37 days ago. Fresh activity helps separate stable projects from stale ones.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-15 01:00 UTC·Repo last pushed 37 days ago
Public trust evidence for mcp-proxy is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for mcp-proxy. 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-proxy actively maintained?
Slowing down. Last push was 37 days ago — keep an eye on whether activity resumes.
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.
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
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-proxy?
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.
