read_contract

4 registry entries were observed exposing a tool named read_contract — none of them flagged as a privileged capability.

Spelled read_contract, read-contract in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @rsksmart/rsk-mcp-serververified
   trust 85/100 · AMCP serverobserved 2026-08-15 · static extraction
   MCP Server for Rootstock Blockchain
2. exchange.merx/mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   TRON energy exchange for AI agents. 54 tools, 30 prompts, 21 resources. A2A + ACP.
3. io.github.json-contracts/json-contracts
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   JSON contract registry and validator for structured LLM and agent outputs.
4. io.github.portdeveloper/gulltoppr
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Resolve any EVM contract ABI (even unverified, via decompilation), read, simulate, prepare txs.

All indexed toolsSearch the registry for read_contract