Is MCPProxy safe to use?

MCPProxy has an HVTrust score of 66.0/100 (Grade B), ranked #438 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCPProxy?

MCPProxy scores 66.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 379 GitHub stars and is categorized under MCP Servers.

MCPProxy

smart-mcp-proxy/mcpproxy-go

Supercharge AI Agents, Safely

MCP Servers Go Listed MIT

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

OSSF Scorecard 6.6 / 10

Provenance None

Signed commits 100%

Last push today

Compare MCPProxy

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCPProxy scores 66.0/100 (Grade B), ranked #438 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCPProxy compares in MCP Servers

#256 MCP Design System Extractor 66.2 +0.2
#257 YADE MCP Server 66.1 +0.1
#258 MCPProxy 66.0 this agent
#259 Umbraco CMS MCP Dev 66.0 ±0
#260 Redmine MCP Server 66.0 ±0

Bars show each HVTrust score; the tick marks MCPProxy’s 66.0.

Where the 66.0 comes from

HVTrust dimensions vs the MCP Servers average

66.0 / 100 · 100.0% confidence

MCPProxy MCP Servers average (775 agents)

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

13.2 / 25

2.9 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

1.9 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.9 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.2 / 20

1.0 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade C → B

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

73.7

Activity sub-score · out of 100

#258

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

379

Forks

Last Push

2026-09-26

today

Commits (4 wk)

197

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #438

Analysis

Activity Inputs

73.7 / 100

StarsRepository reach

15.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Sep 17, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 7

SAST 10

Security-Policy 10

Signed-Releases 10

Token-Permissions 0

Vulnerabilities 0

Common questions about MCPProxy

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

No published build provenance is currently detected for MCPProxy. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCPProxy have an OpenSSF Scorecard?

MCPProxy has an OpenSSF Scorecard score of 6.6/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 MCPProxy actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does MCPProxy use?

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

Are MCPProxy's commits signed?

100% of the last 100 commits to MCPProxy 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

MCPProxy 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

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 MCPProxy'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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCPProxy?

For maintainers

HVTrust scores MCPProxy 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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade C → B

2026-09-23

Rank Moved

Rank dropped 96 spots (#340 → #436)

2026-09-23

HVTrust Changed

HVTrust up 15.3pts (50.7 → 66.0)

2026-09-22

Newly Listed

First tracked at rank #340

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 16 spots (#452 → #436)

2026-09-10

Rank Moved

Rank dropped 10 spots (#428 → #438)

2026-09-09

Rank Moved

Rank dropped 20 spots (#408 → #428)

2026-09-07

Rank Moved

Rank dropped 23 spots (#377 → #400)

2026-09-05

Rank Moved

Rank dropped 69 spots (#303 → #372)

2026-09-03

Rank Moved

Rank dropped 32 spots (#262 → #294)

2026-08-31

Rank Moved

Rank dropped 25 spots (#233 → #258)

2026-08-29

Rank Moved

Rank dropped 18 spots (#222 → #240)

2026-08-27

Rank Moved

Rank dropped 10 spots (#209 → #219)

2026-08-26

Rank Moved

Rank dropped 15 spots (#194 → #209)

2026-08-22

Rank Moved

Rank rose 11 spots (#196 → #185)

2026-08-17

Rank Moved

Rank rose 13 spots (#195 → #182)

2026-08-13

Rank Moved

Rank dropped 12 spots (#174 → #186)

2026-08-12

Rank Moved

Rank rose 12 spots (#186 → #174)

2026-08-10

Rank Moved

Rank dropped 10 spots (#173 → #183)

2026-08-08

Newly Listed

First tracked at rank #170

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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