BlockReq

Read-only BlockReq docs, network catalog, and JSON-RPC calls across EVM chains

使うべきか

品質と安全性

A
説明の品質
97%
スキーマの完全性
97%
命名の品質
100%
ポイズニングのリスク
60%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'list_chains' description contains placeholder textlist_chains 内
  • MEDIUMTool description contains URL to non-standard domainget_doc_page 内
  • INFOTool description contains placeholder or incomplete textlist_chains 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,003トークン数(ツール定義)
~958 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.78%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "rpc": {
      "url": "https://mcp.blockreq.com/mcp"
    }
  }
}

リモートエンドポイント

https://mcp.blockreq.com/mcpstreamable-http
https://mcp.blockreq.com/mcp/accountstreamable-http

できること

ツール一覧

ツール(6)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢list_chains(network_type)

List every published BlockReq network with its host, public trial URL, private URL pattern ({API_KEY} placeholder), WSS support, and archive and proof/debug/trace flags.

入力スキーマ

{
  "type": "object",
  "properties": {
    "network_type": {
      "type": "string",
      "enum": [
        "mainnet",
        "testnet",
        "beacon"
      ],
      "description": "Only this network type"
    }
  },
  "additionalProperties": false
}
🟢get_chain(chain)

Get one network's URLs and capability flags, its API reference page, and (for EVM networks) the JSON-RPC methods documented for it.

入力スキーマ

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "description": "Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)"
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false
}
🟢search_docs(query, locale, limit)

Search the BlockReq docs (setup, API keys, endpoints, Request Counting, plans, networks, support). Returns page titles, URLs, Markdown URLs for get_doc_page, and snippets. Chinese queries search the Chinese pages.

入力スキーマ

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Words to search for"
    },
    "locale": {
      "type": "string",
      "enum": [
        "en",
        "zh-cn"
      ],
      "description": "Docs language; defaults to the query's language"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "description": "Most results to return (default 5)"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢get_doc_page(url)

Read one BlockReq docs page as Markdown. Accepts a https://blockreq.com/docs/... URL (HTML or index.md) or a path such as /docs/getting-started/.

入力スキーマ

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Docs page URL or path"
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢get_method_reference(chain, method)

Get the documented parameters, result, example, and endpoints of one JSON-RPC method on one EVM network, from BlockReq's OpenRPC document.

入力スキーマ

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "description": "Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)"
    },
    "method": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "JSON-RPC method, for example eth_getLogs"
    }
  },
  "required": [
    "chain",
    "method"
  ],
  "additionalProperties": false
}
🟢call_rpc(chain, method, params)

Call one read-only JSON-RPC method on an EVM network. Without credentials it uses the public trial endpoint (rate-limited, recent state only); when this MCP connection sends a BlockReq API key or is signed in to a BlockReq account, it uses the caller's own endpoint, metered to their account with their plan's limits and history. eth_getLogs needs numeric fromBlock/toBlock at most 1000 blocks apart, or a blockHash. Responses above 256 KB are refused. It cannot sign or send transactions.

入力スキーマ

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "description": "Network slug (for example ethereum, base, arbitrum-sepolia), catalog id, hostname, name, or EVM chain ID (1 or 0x1)"
    },
    "method": {
      "type": "string",
      "enum": [
        "eth_blockNumber",
        "eth_chainId",
        "eth_getBalance",
        "eth_call",
        "eth_getLogs",
        "eth_getTransactionByHash",
        "eth_getTransactionReceipt",
        "eth_getCode",
        "eth_getStorageAt",
        "eth_getBlockByNumber"
      ]
    },
    "params": {
      "type": "array",
      "description": "Positional JSON-RPC params; a missing block parameter means latest"
    }
  },
  "required": [
    "chain",
    "method"
  ],
  "additionalProperties": false
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 6 件