BlockReq

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
97%
Integridad del esquema
97%
Calidad de los nombres
100%
Riesgo de envenenamiento
60%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'list_chains' description contains placeholder texten list_chains
  • MEDIUMTool description contains URL to non-standard domainen get_doc_page
  • INFOTool description contains placeholder or incomplete texten list_chains

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,003Tokens (definiciones de herramientas)
~958 BTamaño de respuesta típico
Impacto moderado en la atención (0.78% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

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

Qué puede hacer

Inventario de herramientas

Herramientas (6)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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/.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada6 herramientas