# BridgeNode MCP (remote · bridgenode.cc)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- remote · `bridgenode.cc`: 64/100 (this document), [markdown](https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode.md), [page](https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode)
- npm · `@bridgenode/mcp`: 36/100, [markdown](https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode-mcp.md), [page](https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode-mcp)

## Channel facts

- Endpoint: `https://bridgenode.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 613 tokens (~204/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http applefanaimail-blip-bridgenode-mcp https://bridgenode.cc/mcp
```

### Codex

```toml
[mcp_servers.applefanaimail-blip-bridgenode-mcp]
url = "https://bridgenode.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "applefanaimail-blip-bridgenode-mcp": {
      "type": "remote",
      "url": "https://bridgenode.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add applefanaimail-blip-bridgenode-mcp --url https://bridgenode.cc/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  applefanaimail-blip-bridgenode-mcp:
    url: "https://bridgenode.cc/mcp"
```

### Other

```json
{
  "mcpServers": {
    "applefanaimail-blip-bridgenode-mcp": {
      "type": "http",
      "url": "https://bridgenode.cc/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-07 (score 64, +8)

- [security improvement] Authorization: unverified → partial
- [security] Tool “chat_completions” rewrote its description, which is the text the model reads
- [security] Tool “list_models” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool “chat_completions” now declares an output schema
- [functional improvement] Tool “list_models” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good
- [functional] New tool “get_price_estimate”
- [cosmetic] Tool “chat_completions” changed its title: Chat completions with x402 payment
- [cosmetic] Tool “list_models” changed its title: List available models and prices

### 2026-08-06 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-05 (score 55)

First indexed and scored.

## MCP tools (3)

### `chat_completions` (~242 tokens)

Chat completions with x402 payment

Send a chat completion request to any supported model. Paid tool: x402 payment (Solana USDC) is required — the first call returns 402 with the exact price; retry with _meta["x402/payment"]. Responses are non-streaming. Provide either mode (auto/eco/premium routing) or model (explicit id, mutually exclusive with mode); one of the two is required — if both are sent, model wins. mode values: auto = cheapest model fitting the context, eco = cheapest available, premium = best model. max_tokens defaults to 4096 and is clamped to the model's max output. Use this tool to generate text; to inspect models and prices first, use the free list_models tool.

Input parameters:

- `max_tokens` (integer): Max output tokens (billed upfront, §4.2). MCP calls are non-stream: cap per config.
- `messages` (array, required): Chat messages (text content only).
- `mode` (string): Smart routing profile (auto/eco/premium).
- `model` (string): Explicit model id (see list_models / /v1/models). Mutually exclusive with mode.

Output parameters:

- `choices` (array)
- `created` (integer)
- `id` (string)
- `model` (string)
- `object` (string)
- `usage` (object)

### `list_models` (~140 tokens)

List available models and prices

List available models and their prices — free, no payment, no authentication required. Read-only: no state changes; data is served from the server's local config, so repeated calls return identical results (idempotent). Accepts no parameters: calling it without arguments returns the complete catalog with per-token prices; there is no filtering, pagination, or configuration. Use this tool to inspect models and prices before calling the paid chat_completions tool. Same data as GET /v1/models (§5.2). Do not use it to generate text (use chat_completions) or to estimate a specific request's cost (use get_price_estimate).

Output parameters:

- `data` (array)
- `object` (string)

### `get_price_estimate` (~231 tokens)

Estimate the cost of a chat request

Estimate the USDC cost of a chat completion request before paying — free, no payment, no authentication required. Read-only: no state changes and no external calls; the estimate is computed locally from server pricing config, so repeated calls with identical inputs return identical results (idempotent). Use this tool to check the exact price for a given model/mode, messages, and max_tokens before calling the paid chat_completions tool. Provide either mode (auto/eco/premium routing) or model (explicit id, mutually exclusive with mode); one of the two is required — if both are sent, model wins. mode values: auto = cheapest model fitting the context, eco = cheapest available, premium = best model.

Input parameters:

- `max_tokens` (integer): Max output tokens to estimate (billed upfront, §4.2).
- `messages` (array, required): Chat messages (text content only).
- `mode` (string): Smart routing profile (auto/eco/premium).
- `model` (string): Explicit model id (see list_models / /v1/models). Mutually exclusive with mode.

Output parameters:

- `amount_atomic` (integer)
- `amount_usdc` (number)
- `input_tokens` (integer)
- `max_tokens_clamped` (integer)
- `model` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode#diagnostics

## Score history

- 2026-08-07: 64
- 2026-08-06: 56
- 2026-08-05: 55

## Links

- Remote endpoint: https://bridgenode.cc/mcp
- Repository: https://github.com/applefanaimail-blip/bridgenode-skill
- Changelog RSS feed: https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode.xml
- Changelog JSON feed: https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode.json
- HTML version of this page: https://verifymcp.io/servers/applefanaimail-blip-bridgenode-mcp/bridgenode