Is Debridge MCP safe to use?

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

What is the trust score for Debridge MCP?

Debridge MCP scores 49.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 31 GitHub stars and is categorized under MCP Servers.

Debridge MCP

Repository

MCP server that gives AI agents the ability to execute cross-chain cryptocurrency swaps and transfers via the deBridge protocol

MCP Servers TypeScript Listed MIT

Is Debridge MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.2 / 10

Provenance None

Signed commits 2%

Last push 4d ago

Advisories None known

Compare Debridge MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Debridge MCP scores 49.9/100 (Grade D), ranked #1016 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.2/10; 2% of recent commits are signed; no published advisory affects its latest release (@debridge-finance/debridge-mcp); last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Debridge MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 64.6 C · #294 of 781
Raise the OSSF Scorecard from 3.2 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.2 → 62.1 C · #346 of 781
Sign every commit2% signed today +4.9 → 54.8 C · #466 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Debridge MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/debridge-finance/debridge-mcp, MIT, last pushed 2026-10-14. 2% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.2/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies3
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- npm @debridge-finance/debridge-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: @debridge-finance/debridge-mcp 0.1.5. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

2026-08-26 OSSF Scorecard: 3.2/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Debridge MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Debridge MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Debridge MCP’s 49.9.

Where the 49.9 comes from

HVTrust dimensions vs the MCP Servers average

49.9 / 100 · 100.0% confidence

Debridge MCP MCP Servers average (781 agents)

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

4.1 / 25

6.5 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.8 below avg 13.6

Transparency50% declared license · 50% OSSF Scorecard

11.2 / 17

1.1 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

0.5 below avg 12.2

AdoptionLog-scaled stars · package downloads

6.1 / 20

1.3 below avg 7.4

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-18

Grade Changed

Trust grade C → D

2026-10-14

Grade Changed

Trust grade D → C

2026-10-14

Rank Moved

Rank rose 12 spots (#1010 → #998)

Maintainer Checklist

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

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

37.2

Activity sub-score · out of 100

#574

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

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars

Forks

Last Push

2026-10-14

4 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #1018

Analysis

Activity Inputs

37.2 / 100

StarsRepository reach

9.0 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.6 / 20

Common questions about Debridge MCP

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

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

Does Debridge MCP have an OpenSSF Scorecard?

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

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

What license does Debridge MCP use?

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

Are Debridge MCP's commits signed?

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

Debridge MCP 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

How this surface has changed

Detected changes to Debridge MCP'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-26

Activity Resumed

Activity resumed

Maintain Debridge MCP?

For maintainers

HVTrust scores Debridge MCP 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-10-18

Grade Changed

Trust grade C → D

2026-10-14

Grade Changed

Trust grade D → C

2026-10-14

Rank Moved

Rank rose 12 spots (#1010 → #998)

2026-10-11

Rank Moved

Rank dropped 11 spots (#990 → #1001)

2026-10-10

Rank Moved

Rank dropped 10 spots (#980 → #990)

2026-10-09

Rank Moved

Rank dropped 14 spots (#966 → #980)

2026-09-30

Rank Moved

Rank rose 19 spots (#978 → #959)

2026-09-25

Rank Moved

Rank dropped 11 spots (#963 → #974)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 169 spots (#1128 → #959)

2026-09-23

HVTrust Changed

HVTrust up 27.5pts (21.5 → 49.0)

2026-09-22

Newly Listed

First tracked at rank #1128

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Grade Changed

Trust grade C → D

2026-09-11

Rank Moved

Rank dropped 14 spots (#911 → #925)

2026-09-09

Grade Changed

Trust grade D → C

2026-09-08

Grade Changed

Trust grade C → D

2026-09-08

Rank Moved

Rank dropped 10 spots (#893 → #903)

2026-09-07

Rank Moved

Rank dropped 47 spots (#846 → #893)

2026-09-06

Rank Moved

Rank dropped 16 spots (#830 → #846)

2026-09-05

Rank Moved

Rank dropped 57 spots (#773 → #830)

2026-09-04

Rank Moved

Rank dropped 31 spots (#742 → #773)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank dropped 36 spots (#706 → #742)

2026-09-02

Rank Moved

Rank rose 371 spots (#1077 → #706)

2026-09-02

HVTrust Changed

HVTrust up 16.4pts (33.5 → 49.9)

2026-09-01

Rank Moved

Rank dropped 44 spots (#1033 → #1077)

2026-08-31

Rank Moved

Rank dropped 33 spots (#1000 → #1033)

2026-08-30

Rank Moved

Rank dropped 52 spots (#948 → #1000)

2026-08-29

Rank Moved

Rank dropped 48 spots (#900 → #948)

2026-08-28

Rank Moved

Rank dropped 31 spots (#869 → #900)

2026-08-27

Rank Moved

Rank dropped 26 spots (#843 → #869)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.2/10

2026-08-26

Activity Resumed

Activity resumed

2026-08-26

Rank Moved

Rank rose 399 spots (#1242 → #843)

2026-08-26

HVTrust Changed

HVTrust up 17.7pts (16.1 → 33.8)

2026-08-26

Activity Score Changed

Activity score up 20pts (17 → 38)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1209 → #1234)

2026-08-10

Rank Moved

Rank dropped 72 spots (#1133 → #1205)

2026-08-08

Newly Listed

First tracked at rank #1128

GitHub → npm: @debridge-finance/debridge-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

Debridge MCP

How Debridge MCP could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Debridge MCP compares in MCP Servers

Where the 49.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Debridge MCP

AI agent surface

Maintain Debridge MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers