Is MCP-Bridge safe to use?

MCP-Bridge has an HVTrust score of 39.8/100 (Grade D), ranked #1168 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP-Bridge?

MCP-Bridge scores 39.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 930 GitHub stars and is categorized under Protocols & Tool Integration.

MCP-Bridge

SecretiveShell/MCP-Bridge

A middleware to provide an openAI compatible endpoint that can call MCP tools

Protocols & Tool Integration Python Grade D Listed MIT

39.8/100

Rank #1168 of 1328

Compare MCP-Bridge

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2025-12-08 · 286d ago

Recent change

No recent signal change

Is MCP-Bridge safe? MCP-Bridge scores 39.8/100 (Grade D), ranked #1168 of 1328 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 4.5/10; 40% of recent commits are signed; last pushed 2025-12-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#54 mcpo — 42.1 (D) → #55 MCP Hub — 40.3 (D) → #57 TUUI — 37.3 (D) → #58 MCP Playwright — 36.9 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-12

Rank Moved

Rank dropped 10 spots (#1154 → #1164)

2026-09-09

Rank Moved

Rank dropped 13 spots (#1138 → #1151)

2026-09-07

Rank Moved

Rank dropped 18 spots (#1111 → #1129)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/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.

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 286 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP-Bridge View Protocols & Tool Integration Report missing data

27.5

Activity sub-score · out of 100

#56

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

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars

930

Forks

119

Last Push

2025-12-08

286 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1169

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

39.8 / 100 · 100.0% confidence

MCP-Bridge Protocols & Tool Integration average (61 agents)

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

7.6 / 25

2.9 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.8

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.0 below avg 14.0

AdoptionLog-scaled stars · package downloads

7.1 / 20

3.5 below avg 10.6

Activity Inputs

27.5 / 100

StarsRepository reach

17.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

40%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 5

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 8

Token-Permissions 9

Vulnerabilities 0

Is MCP-Bridge safe?

Public trust evidence for MCP-Bridge 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-Bridge publish package provenance?

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

Does MCP-Bridge have an OpenSSF Scorecard?

MCP-Bridge has an OpenSSF Scorecard score of 4.5/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-Bridge actively maintained?

Stale. The repository has not been pushed to in 286 days. Consider whether the project is still being maintained.

What license does MCP-Bridge use?

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

Are MCP-Bridge's commits signed?

40% of the last 100 commits to MCP-Bridge 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

MCP-Bridge 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.

Postgres

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

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

Maintain MCP-Bridge?

For maintainers

HVTrust scores MCP-Bridge 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-12

Rank Moved

Rank dropped 10 spots (#1154 → #1164)

2026-09-09

Rank Moved

Rank dropped 13 spots (#1138 → #1151)

2026-09-07

Rank Moved

Rank dropped 18 spots (#1111 → #1129)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1096 → #1111)

2026-09-05

Rank Moved

Rank dropped 37 spots (#1059 → #1096)

2026-09-04

Rank Moved

Rank dropped 25 spots (#1034 → #1059)

2026-09-03

Rank Moved

Rank dropped 61 spots (#973 → #1034)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.5/10

2026-09-02

Rank Moved

Rank rose 322 spots (#1295 → #973)

2026-09-02

HVTrust Changed

HVTrust up 23.6pts (16.2 → 39.8)

2026-08-26

Rank Moved

Rank dropped 21 spots (#1236 → #1257)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1212 → #1237)

2026-08-10

Rank Moved

Rank dropped 72 spots (#1140 → #1212)

2026-08-08

Rank Moved

Rank dropped 630 spots (#507 → #1137)

2026-08-06

Newly Listed

First tracked at rank #518

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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