# BridgeNode MCP (remote · bridgenode.cc)

BridgeNode — x402 pay-per-request AI inference. OpenAI-compatible API + MCP, Solana USDC, gas-free.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `bridgenode.cc`: 83/100 (this document), [markdown](https://verifymcp.io/servers/bridgenode-ai-bridgenode-mcp/bridgenode.md), [page](https://verifymcp.io/servers/bridgenode-ai-bridgenode-mcp/bridgenode)
- npm · `@bridgenode/mcp`: 39/100, [markdown](https://verifymcp.io/servers/bridgenode-ai-bridgenode-mcp/bridgenode-mcp.md), [page](https://verifymcp.io/servers/bridgenode-ai-bridgenode-mcp/bridgenode-mcp)

## Channel facts

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

## 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-09-20.

- **Endpoint Security**: 69/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 773 tokens (~193/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the BridgeNode MCP server?

BridgeNode MCP is a hosted endpoint at https://bridgenode.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http bridgenode-ai-bridgenode-mcp 'https://bridgenode.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bridgenode-ai-bridgenode-mcp": {
      "url": "https://bridgenode.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bridgenode-ai-bridgenode-mcp": {
      "type": "http",
      "url": "https://bridgenode.cc/mcp"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "bridgenode-ai-bridgenode-mcp": {
      "Transport": "http",
      "Url": "https://bridgenode.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bridgenode-ai-bridgenode-mcp -t streamable-http -u 'https://bridgenode.cc/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bridgenode-ai-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-09-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 80, 0)

- [security] Tool “chat_completions” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 155 → 193
- [functional] Schema quality: good → excellent
- [cosmetic] “chat_completions” added an optional parameter “tool_choice”
- [cosmetic] “chat_completions” added an optional parameter “tools”
- [cosmetic] “chat_completions” reworded the description of “max_tokens”
- [cosmetic] “chat_completions” reworded the description of “messages”

### 2026-09-12 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 79, +1)

- [security] Tool “chat_completions” rewrote its description, which is the text the model reads
- [functional] Server version: 1.5.5 → 1.7.0
- [functional] Server version: 1.5.4 → 1.5.5

### 2026-09-09 (score 78, 0)

- [functional] Server version: 1.5.1 → 1.5.4
- [functional] Server version: 1.5.0 → 1.5.1
- [functional] Server version: 1.4.1 → 1.5.0

### 2026-09-08 (score 78, +1)

- [functional] Server version: 1.4.0 → 1.4.1
- [functional] Server version: 1.3.0 → 1.4.0

## MCP tools (3)

### `chat_completions` (~370 tokens)

Chat completions with x402 payment

Send a chat completion request to any supported model. Free models are served without payment; the first calls to a PAID model are also free per client (free trials), after which x402 payment (Solana USDC) is required — an unpaid call returns 402 with the exact price; retry with _meta["x402/payment"]. Responses are non-streaming. Pass either mode (auto/eco/premium) or model (explicit id) — one of the two is required; model wins if both are sent. Use this tool to generate text; inspect models and prices first with the free list_models tool. Start with a FREE model (no payment at all) and keep max_tokens >= 200 — a thinking model spends part of that budget on reasoning, so a smaller limit can return an empty answer.

Input parameters:

- `max_tokens` (integer): Max output tokens (billed upfront, §4.2). MCP calls are non-stream: cap per config. Use >= 200 — reasoning models share this budget with their thinking and a smaller limit can return an empty answer.
- `messages` (array, required): Chat messages (text content only). An assistant turn that calls a tool may carry content: null with tool_calls.
- `mode` (string): Smart routing profile (auto/eco/premium).
- `model` (string): Explicit model id (see list_models / /v1/models). Mutually exclusive with mode.
- `tool_choice` (string|object): OpenAI tool_choice: 'auto', 'none', 'required', or {type: function, function: {name}}.
- `tools` (array): OpenAI-style tool schemas the model may call. Forwarded unchanged; they count as input tokens for the price (§4.2/§5.3).

Output parameters:

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

### `list_models` (~155 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: the input schema is an empty object, and any arguments passed are ignored. 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/bridgenode-ai-bridgenode-mcp/bridgenode#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72
- 2026-08-26: 72
- 2026-08-25: 70
- 2026-08-24: 69
- 2026-08-23: 69

## Common questions

### What is the BridgeNode MCP server?

BridgeNode MCP is listed in the public MCP registry as io.github.bridgenode-ai/bridgenode-mcp. BridgeNode, x402 pay-per-request AI inference. OpenAI-compatible API + MCP, Solana USDC, gas-free. This page covers its hosted endpoint (https://bridgenode.cc/mcp).

### Is the BridgeNode MCP server safe to use?

BridgeNode MCP scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BridgeNode MCP server expose?

BridgeNode MCP exposes 3 tools: chat_completions, list_models, get_price_estimate. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

### Does the BridgeNode MCP server require authentication?

No. We connected to BridgeNode MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BridgeNode MCP server still maintained?

BridgeNode MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

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