Skip to main content
Glama
@bridgenode/mcp

@bridgenode/mcp

Official

@bridgenode/mcp

npm version npm downloads License: MIT-0 CI Website BridgeNode on x402-list

AIエージェント向けに構築 — APIキー不要、登録不要、x402経由でSolana USDCによる従量課金制。

BridgeNode MCPラッパー — リモートのhttps://bridgenode.cc/mcp(streamable-HTTP)へのリクエストを自動x402決済(Solana USDC)付きでプロキシするstdio MCPサーバです。APIキー不要、登録不要。

インストール(ワンコマンド)

claude mcp add bridgenode -s user -- npx -y @bridgenode/mcp@latest

または手動(Claude Code、Cursor、その他のMCPクライアント):

{
  "mcpServers": {
    "bridgenode": {
      "command": "npx",
      "args": ["-y", "@bridgenode/mcp@latest"]
    }
  }
}

Related MCP server: @hpp-io/x402-mcp-bridge

設定(.env)

# Solana wallet private key (base58) — agent's payment wallet
BRIDGENODE_WALLET_KEY=

# Spending policy (fail-closed)
BRIDGENODE_MAX_PER_CALL=0.05
BRIDGENODE_DAILY_CAP=1.0

ツール

  • chat_completions — AI推論(有料。x402決済は自動)

  • list_models — モデル一覧(無料)

  • get_price_estimate — チャットリクエストのコスト見積もり(無料)

仕組み

  1. ローカルMCPクライアントがstdio経由でラッパーを起動する

  2. ラッパーがhttps://bridgenode.cc/mcp(streamable HTTP)に接続する

  3. tools/callが402(支払い要求)を受け取ると、ラッパーは自動的に BRIDGENODE_WALLET_KEYで支払いに署名し、リクエストを再試行する

  4. 支払いポリシーは署名の前に毎回の支払いをチェックする(fail-closed)

リンク

Pythonパッケージ

Pythonの方がお好みですか?同じBridgeNodeツールキットがPyPIにあります:

コミュニティ

Available Tools

3 tools
chat_completionsChat completions with x402 paymentAInspect

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.

Inputs: messages (required), mode, model, tools, +2 more. Returns: id, model, usage, object, +2 more

get_price_estimateEstimate the cost of a chat requestA
Read-onlyIdempotent
Inspect

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.

Inputs: messages (required), mode, model, max_tokens. Returns: model, amount_usdc, input_tokens, amount_atomic, +1 more

list_modelsList available models and pricesA
Read-onlyIdempotent
Inspect

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).

Inputs: no named parameters. Returns: data, object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: list_models returns the catalog, get_price_estimate prices a specific request, and chat_completions performs inference. The descriptions explicitly cross-reference each other ('use chat_completions', 'use get_price_estimate'), eliminating any realistic misselection.

    Naming Consistency4/5

    get_price_estimate and list_models follow a clean verb_noun pattern, but chat_completions is a bare noun naming a resource/action endpoint. The deviation is minor and the naming remains predictable and readable.

    Tool Count4/5

    Three tools is lean but plausibly matches the narrow gateway scope: inspect models, estimate cost, generate text. It sits at the low edge of the ideal range, with little redundancy, though it leaves almost no room for ancillary operations.

    Completeness4/5

    The core pay-per-request lifecycle (discover models, price a request, execute) is fully covered, including the 402 payment retry flow. Minor gaps exist: no streaming option, no balance/usage or payment-status tool, and no embeddings or other model modalities.

    Maintenance

    ActivitySlowing
    ResponsivenessMostly unanswered

    Related MCP Connectors

    Related MCP Servers