BridgeNode MCP
REMOTE · BRIDGENODE.CC · 2 COMPONENTS · SCANNED SEP 20
BridgeNode — x402 pay-per-request AI inference. OpenAI-compatible API + MCP, Solana USDC, gas-free.
Available components
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · bridgenode.cc
claude mcp add --transport http bridgenode-ai-bridgenode-mcp 'https://bridgenode.cc/mcp'
{
"mcpServers": {
"bridgenode-ai-bridgenode-mcp": {
"url": "https://bridgenode.cc/mcp"
}
}
} {
"servers": {
"bridgenode-ai-bridgenode-mcp": {
"type": "http",
"url": "https://bridgenode.cc/mcp"
}
}
} [mcp_servers.bridgenode-ai-bridgenode-mcp] url = "https://bridgenode.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bridgenode-ai-bridgenode-mcp": {
"type": "remote",
"url": "https://bridgenode.cc/mcp",
"enabled": true
}
}
} openclaw mcp add bridgenode-ai-bridgenode-mcp --url 'https://bridgenode.cc/mcp' --transport streamable-http
mcp_servers:
bridgenode-ai-bridgenode-mcp:
url: "https://bridgenode.cc/mcp" {
"McpServers": {
"bridgenode-ai-bridgenode-mcp": {
"Transport": "http",
"Url": "https://bridgenode.cc/mcp"
}
}
} assistant mcp add bridgenode-ai-bridgenode-mcp -t streamable-http -u 'https://bridgenode.cc/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 14 Sept 26 0
- Tool “chat_completions” rewrote its description, which is the text the model reads security
- Schema quality: 155 → 193 ▼ functional
- Schema quality: good → excellent functional
- “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” cosmetic
- 12 Sept 26 +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.
- 10 Sept 26 +1
- Tool “chat_completions” rewrote its description, which is the text the model reads security
- Server version: 1.5.5 → 1.7.0 functional
- Server version: 1.5.4 → 1.5.5 functional
- 9 Sept 26 0
- 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 functional
- 8 Sept 26 +1
- Server version: 1.4.0 → 1.4.1 functional
- Server version: 1.3.0 → 1.4.0 functional
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 20 Sept 2026 · Probed https://bridgenode.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bridgenode.cc | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8613068d7c5f37a40e3b245035a59d1c |
| SANs: bridgenode.cc, *.bridgenode.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bridgenode.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| bridgenode.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://24klabs.ai https://x402-list.com https://nohumans.directory; script-src 'self' 'unsafe-inline'; connect-src 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bridgenode.cc/mcp | Verified | 200 | |
| http (plaintext) | http://bridgenode.cc/mcp | Inconclusive | 405 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chat_completions Chat completions with x402 payment ~370
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| choices | array | – | – |
| created | integer | – | – |
| id | string | – | – |
| model | string | – | – |
| object | string | – | – |
| usage | object | – | – |
No examples provided.
get_price_estimate Estimate the cost of a chat request ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Max output tokens to estimate (billed upfront, §4.2). |
| messages | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_atomic | integer | – | – |
| amount_usdc | number | – | – |
| input_tokens | integer | – | – |
| max_tokens_clamped | integer | – | – |
| model | string | – | – |
No examples provided.
list_models List available models and prices ~155
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).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| object | string | – | – |
No examples provided.
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.