Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BridgeNode MCP

NPM · @BRIDGENODE/MCP · 2 COMPONENTS · SCANNED AUG 7

AI inference via MCP — pay per request with Solana USDC through x402. No API keys.

Available components

remote · bridgenode.cc 64 npm · @bridgenode/mcp 36
36 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 146 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @bridgenode/mcp

# add to Claude Code
claude mcp add applefanaimail-blip-bridgenode-mcp -- npx -y @bridgenode/mcp
# add to Codex CLI
codex mcp add applefanaimail-blip-bridgenode-mcp -- npx -y @bridgenode/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "applefanaimail-blip-bridgenode-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@bridgenode/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add applefanaimail-blip-bridgenode-mcp --command npx --arg -y --arg @bridgenode/mcp
# ~/.hermes/config.yaml
mcp_servers:
  applefanaimail-blip-bridgenode-mcp:
    command: "npx"
    args: ["-y", "@bridgenode/mcp"]
// mcp.json
{
  "mcpServers": {
    "applefanaimail-blip-bridgenode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bridgenode/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Aug 26 +2
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.92 functional
  • 5 Aug 26 34

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/@bridgenode/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 146 packages
Packages resolved 146
Stale 30
Tree resolution Complete
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.