bridgenode
Registry code: a4109a6dccfe5daa
BridgeNode MCP wrapper — stdio MCP server proxying to remote streamable-HTTP /mcp with automatic x402 payments (Solana USDC). No API keys.
from a public catalogue that lists it, not from the operator
- endpoint
- https://bridgenode.cc/mcp
- door code
- dc3f25c5afd334b7
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is bridgenode live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is bridgenode free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does bridgenode have?
- 3 tools: chat_completions, get_price_estimate, list_models.
- Is bridgenode safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.3%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- send a chat completion to a model
- estimate the cost of a completion
- list available models and prices
- takes → gives
- text → text
- tools
- 3 reads
- note
- resells another provider
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_models reads open 24h ago
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).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "description": "Accepts no parameters — empty object; any arguments passed are ignored." }arguments 6 lineschat_completions reads unknown never probed
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.
{ "type": "object", "anyOf": [ { "required": [ "model" ] }, { "required": [ "mode" ] } ], "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "messages" ], "properties": { "mode": { "enum": [ "auto", "eco", "premium" ], "type": "string", "description": "Smart routing profile (auto/eco/premium)." }, "model": { "type": "string", "description": "Explicit model id (see list_models / /v1/models). Mutually exclusive with mode." }, "tools": { "type": "array", "items": { "type": "object", "required": [ "type", "function" ], "properties": { "type": { "enum": [ "function" ], "type": "string" }, "function": { "type": "object" } } }, "description": "OpenAI-style tool schemas the model may call. Forwarded unchanged; they count as input tokens for the price (§4.2/§5.3)." }, "messages": { "type": "array", "items": { "type": "object", "required": [ "role" ], "properties": { "role": { "enum": [ "system", "user", "assistant", "tool" ], "type": "string" }, "content": { "type": [ "string", "null" ] }, "tool_calls": { "type": "array" }, "tool_call_id": { "type": "string" } } }, "description": "Chat messages (text content only). An assistant turn that calls a tool may carry content: null with tool_calls." }, "max_tokens": { "type": "integer", "minimum": 1, "description": "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." }, "tool_choice": { "type": [ "string", "object" ], "description": "OpenAI tool_choice: 'auto', 'none', 'required', or {type: function, function: {name}}." } } }arguments 101 linesget_price_estimate reads unknown 24h ago
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.
{ "type": "object", "anyOf": [ { "required": [ "model" ] }, { "required": [ "mode" ] } ], "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "messages" ], "properties": { "mode": { "enum": [ "auto", "eco", "premium" ], "type": "string", "description": "Smart routing profile (auto/eco/premium)." }, "model": { "type": "string", "description": "Explicit model id (see list_models / /v1/models). Mutually exclusive with mode." }, "messages": { "type": "array", "items": { "type": "object", "required": [ "role", "content" ], "properties": { "role": { "enum": [ "system", "user", "assistant", "tool" ], "type": "string" }, "content": { "type": "string" } } }, "description": "Chat messages (text content only)." }, "max_tokens": { "type": "integer", "minimum": 1, "description": "Max output tokens to estimate (billed upfront, §4.2)." } } }arguments 64 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida4109a6dccfe5daa.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a4109a6dccfe5daa/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a4109a6dccfe5daa?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 2
- ok
- 0
- failed
- 2
- success rate
- 0%
- median latency
- 45ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
2 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.