updated 2026-10-16 20:06 UTC

Crabeye MCP Bridge

Repository

MCP bridge to other MCP tools, which includes search and allows potentially thousands of tools to be available without incurring in higher token usage.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.3 / 10
Provenance None
Signed commits 0%
Last push yesterday
Advisories None known
Compare Crabeye MCP Bridge

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Crabeye MCP Bridge scores 53.9/100 (Grade C), ranked #874 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.3/10; recent commits are unsigned; no published advisory affects its latest release (@crabeye-ai/crabeye-mcp-bridge); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Crabeye MCP Bridge 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.

  1. Source Unsigned

    github.com/crabeye-ai/crabeye-mcp-bridge, MIT, last pushed 2026-10-15. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.3/10 (scanned Oct 16, 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 -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @crabeye-ai/crabeye-mcp-bridge 1.3.0. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 3.1/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 Crabeye MCP Bridge’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 Crabeye MCP Bridge compares in MCP Servers

  1. #478 SunoMCP 54.1 +0.2
  2. #479 TONNode — TON blockchain access 53.9 ±0
  3. #480 Crabeye MCP Bridge 53.9 this agent
  4. #481 GPU MCP Server 53.8 −0.1
  5. #482 NinjaOne 53.8 −0.1

Bars show each HVTrust score; the tick marks Crabeye MCP Bridge’s 53.9.

Where the 53.9 comes from

HVTrust dimensions vs the MCP Servers average

53.9 / 100 · 100.0% confidence

Crabeye MCP Bridge MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
6.4 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
1.0 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
4.5 above avg 12.3
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.2 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-16
Rank Moved
Rank rose 12 spots (#886 → #874)
2026-10-12
Rank Moved
Rank rose 11 spots (#896 → #885)
2026-10-09
Rank Moved
Rank dropped 17 spots (#881 → #898)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/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 Crabeye MCP Bridge View MCP Servers Report missing data
48.8
Activity sub-score · out of 100
#480
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 C 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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
15
Forks
1
Last Push
2026-10-15
yesterday
Commits (4 wk)
16
Downloads (7d)
56
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲12
was #886

Analysis

Activity Inputs

48.8 / 100
StarsRepository reach
7.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
1.4 / 20

Common questions about Crabeye MCP Bridge

Public trust evidence for Crabeye 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 Crabeye MCP Bridge publish package provenance?
No published build provenance is currently detected for Crabeye 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 Crabeye MCP Bridge have an OpenSSF Scorecard?
Crabeye MCP Bridge has an OpenSSF Scorecard score of 3.3/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 Crabeye MCP Bridge actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Crabeye MCP Bridge use?
Crabeye MCP Bridge ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Crabeye MCP Bridge's commits signed?
0% of the last 100 commits to Crabeye 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
Crabeye 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.
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
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 Crabeye MCP Bridge'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-27
Activity Resumed
Activity resumed
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-17
Activity Went Stale
No commits for 90 days

Maintain Crabeye MCP Bridge?

For maintainers

HVTrust scores Crabeye 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
Rank 28HVTrust 5Listed 2Score 2Scorecard 1Stale 1Delisted 1MCP 1Surface 1Surface 1Fresh 1Grade 1
2026-10-16
Rank Moved
Rank rose 12 spots (#886 → #874)
2026-10-12
Rank Moved
Rank rose 11 spots (#896 → #885)
2026-10-09
Rank Moved
Rank dropped 17 spots (#881 → #898)
2026-10-05
Grade Changed
Trust grade D → C
2026-10-05
Rank Moved
Rank rose 101 spots (#983 → #882)
2026-10-05
HVTrust Changed
HVTrust up 3.5pts (49.0 → 52.5)
2026-10-03
Rank Moved
Rank rose 15 spots (#993 → #978)
2026-10-02
Rank Moved
Rank rose 20 spots (#1013 → #993)
2026-10-02
Activity Score Changed
Activity score up 6pts (37 → 42)
2026-09-27
Activity Resumed
Activity resumed
2026-09-27
Rank Moved
Rank rose 154 spots (#1157 → #1003)
2026-09-27
HVTrust Changed
HVTrust up 7.2pts (40.5 → 47.7)
2026-09-27
Activity Score Changed
Activity score up 17pts (20 → 37)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 81 spots (#1236 → #1155)
2026-09-23
HVTrust Changed
HVTrust up 24.2pts (16.4 → 40.6)
2026-09-22
Newly Listed
First tracked at rank #1236
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 15 spots (#1137 → #1152)
2026-09-18
Rank Moved
Rank dropped 15 spots (#1124 → #1139)
2026-09-17
Activity Went Stale
No commits for 90 days
2026-09-16
Rank Moved
Rank rose 10 spots (#1128 → #1118)
2026-09-12
Rank Moved
Rank dropped 16 spots (#1106 → #1122)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1084 → #1100)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1074 → #1084)
2026-09-07
Rank Moved
Rank dropped 35 spots (#1039 → #1074)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1023 → #1039)
2026-09-05
Rank Moved
Rank dropped 58 spots (#965 → #1023)
2026-09-04
Rank Moved
Rank dropped 26 spots (#939 → #965)
2026-09-03
Rank Moved
Rank dropped 58 spots (#881 → #939)
2026-09-02
Rank Moved
Rank rose 251 spots (#1132 → #881)
2026-09-02
HVTrust Changed
HVTrust up 14.3pts (29.5 → 43.8)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1090 → #1132)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1061 → #1090)
2026-08-30
Rank Moved
Rank dropped 55 spots (#1006 → #1061)
2026-08-29
Rank Moved
Rank dropped 50 spots (#956 → #1006)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-28
Rank Moved
Rank rose 281 spots (#1237 → #956)
2026-08-28
HVTrust Changed
HVTrust up 12.1pts (17.5 → 29.6)
2026-08-26
Rank Moved
Rank dropped 30 spots (#1198 → #1228)
2026-08-16
Rank Moved
Rank dropped 23 spots (#1166 → #1189)
2026-08-10
Rank Moved
Rank dropped 71 spots (#1092 → #1163)
2026-08-08
Newly Listed
First tracked at rank #1090
GitHub → npm: @crabeye-ai/crabeye-mcp-bridge

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/crabeye-mcp-bridge.svg)](https://hvtracker.net/agents/crabeye-mcp-bridge)
HTML:
<a href="https://hvtracker.net/agents/crabeye-mcp-bridge"><img src="https://hvtracker.net/badge/crabeye-mcp-bridge.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