updated 2026-08-06 16:30 UTC

MCP-Bridge

SecretiveShell/MCP-Bridge

Pending first signal refresh

Protocols & Tool Integration Python Grade D Listed
8.9/100
Rank #518 of 522
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 D · 1/5 signals
Last push
2025-12-08 · 241d ago
Recent change
New

Is MCP-Bridge safe? MCP-Bridge scores 8.9/100 (Grade D), ranked #518 of 522 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2025-12-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#40 arcade-mcp — 16.6 (D) → #41 MCPJungle — 15.6 (D) → #42 code-mode — 13.6 (D) → #43 golf — 11.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-06
Newly Listed
First tracked at rank #518
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 241 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.4
Activity sub-score · out of 100
#44
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-06 16:30 UTC · Repo last pushed 241 days ago — may be stale

Activity & Reach

Stars
928
Forks
117
Last Push
2025-12-08
241 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
22
Rank Change
NEW

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

8.9 / 100 · 50.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
9.2 below avg 9.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
10.2 below avg 10.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.9 below avg 14.9
AdoptionLog-scaled stars · package downloads
7.1 / 20
3.5 below avg 10.6

Activity Inputs

27.4 / 100
StarsRepository reach
17.8 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
—
Unable to query

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?
No OpenSSF Scorecard data is currently published for MCP-Bridge. 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-Bridge actively maintained?
Stale. The repository has not been pushed to in 241 days. Consider whether the project is still being maintained.
What license does MCP-Bridge use?
MCP-Bridge ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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
None detected
No MCP server signal detected.
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
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
Listed 1
2026-08-06
Newly Listed
First tracked at rank #518
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 8.9 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON