Back to Browse

Legible Check MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

On-chain RPC data for AI agents: block, gas, balance, tokens, receipts, decode. x402 USDC.

About

On-chain RPC data for AI agents: block, gas, balance, tokens, receipts, decode. x402 USDC.

Remote endpoints: streamable-http: https://legible-check.ezealfa.workers.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

15 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-ezealfaro-legible-check": {
      "url": "https://legible-check.ezealfa.workers.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

legible-check — pay-per-call data tools for AI agents (x402 + MCP)

Legible Check MCP server Powered by RustChain

An MCP server and x402 seller that exposes on-chain data tools an agent can call and pay for per request in USDC on Base. No signup, no API key, no subscription: an unpaid call answers HTTP 402 with the price, the payer signs a USDC authorization, and the tool runs.

  • MCP endpoint (Streamable HTTP): https://legible-check.ezealfa.workers.dev/mcp
  • OpenAPI: https://legible-check.ezealfa.workers.dev/openapi.json
  • Health: https://legible-check.ezealfa.workers.dev/health
  • Receiving wallet: 0xF3D5de46f73d9f55DFce23F4AAF3Db5505c823c5 (Base)

Connect from an MCP client

{
  "mcpServers": {
    "legible-check": {
      "type": "streamable-http",
      "url": "https://legible-check.ezealfa.workers.dev/mcp"
    }
  }
}

The server answers JSON-RPC 2.0 over POST /mcp, and also in text/event-stream frames when the client sends Accept: text/event-stream.

Methods: initialize, tools/list, tools/call.

Tools

toolprice (USDC)what it returns
evm_block0.001block number, timestamp, base fee, gas used, tx count
evm_gas0.001gas price split into base and priority fee
evm_balance0.002native balance in wei and native units
evm_token_balance0.003ERC20 balance with decimals and symbol
evm_nonce0.002next transaction nonce
evm_tx0.002decoded transaction by hash
evm_tx_status0.001success / reverted / pending with confirmations
evm_receipt0.002receipt: status, block, gas used, effective gas price
evm_transfers0.003ERC20 transfers for an address over N blocks
evm_token_info0.002name, symbol, decimals, total supply
evm_contract0.003is-contract check, bytecode size, Sourcify ABI
evm_portfolio0.005native balance + nonce + up to 10 token balances in one call
evm_decode0.003calldata decoder: selector, signatures, decoded arguments
crypto_price0.001live prices with 24h change and market cap
dex_quote0.002DEX pair quotes with liquidity and 24h volume
arena_commit_reveal_roll0.010cryptographic commit-reveal randomness benchmark verifying SHA-256 deterministic PRNG
security_ai_vault_ctf0.050AI red-teaming security challenge (CTF / Bug Bounty): adversarial prompt injection test

Chains: base, polygon, arbitrum (pass ?chain= on HTTP, or chain in the tool arguments).

How payment works

  1. Call a tool without payment. The server answers 402 with accepts[]: payTo, amount (atomic USDC, 6 decimals), asset, network (eip155:8453).
  2. Sign an EIP-3009 TransferWithAuthorization for that amount.
  3. Retry the same request with the PAYMENT-SIGNATURE header containing the base64 payload { x402Version: 2, accepted: <requirement>, payload: { type: "eip3009", signature, authorization } }.
  4. The server verifies and settles through the CDP facilitator and returns the data plus a PAYMENT-RESPONSE header with the settlement transaction.

Parameter names are query parameters on HTTP (?address=, ?token=, ?hash=, ?chain=). Unsupported chains are rejected with 400 before any payment is requested.

Why this exists

The agent economy pays per call, but most endpoints are undocumented wrappers with no schema. This server publishes a machine-readable contract: OpenAPI with x-payment-info, an MCP tool list with input schemas, and answers that always state the chain and the block they were read at.

Research & Security Compliance

All tools, benchmarks, and challenges provided by this server are strictly for autonomous AI agent research, cryptographic protocol evaluation, and cybersecurity red-teaming:

  • arena_commit_reveal_roll demonstrates deterministic SHA-256 pseudo-random commit-reveal verification.
  • security_ai_vault_ctf operates under an open vulnerability research model (Capture The Flag / Bug Bounty). Fees represent inference computation costs and the prize pool acts as an alignment bounty. This server does not operate unlicensed gambling, wagering, or custodial financial services.

License

MIT

Reviews

No reviews yet

Be the first to review this server!