Skip to content

MCPFax On-Chain Toolkit

by mcpscores.com · remote · no sign-in to list tools · v1.0.2 · published by com.mcpscores

The on-chain facts you need in the seconds before you transact.

Changes · 4

6 tools: 4 change things and 2 only read.

Scanned Oct 21, 2026

3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http onchain-toolkit https://onchain-toolkit.bowling-anthony.workers.dev/mcp

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The input schema at properties.address.examples[0] contains a 42-character base64 string.

    Matched text

    inputSchema.properties.address.examples[0]: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

    What this check looks for
  • The input schema at properties.address.examples[0] contains a 42-character base64 string.

    Matched text

    inputSchema.properties.address.examples[0]: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"

    What this check looks for
  • The input schema at properties.token.examples[0] contains a 42-character base64 string.

    Matched text

    inputSchema.properties.token.examples[0]: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 4Claude Code: ask
  • address_infoNative balance, the next nonce to use, and whether the address holds contract code — the three things needed before sending from or to an address.2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Warn

      The input schema at properties.address.examples[0] contains a 42-character base64 string.

      Matched text

      inputSchema.properties.address.examples[0]: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"

      What this check looks for
    • Warn

      The input schema at properties.token.examples[0] contains a 42-character base64 string.

      Matched text

      inputSchema.properties.token.examples[0]: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

      What this check looks for
    Description, as the server wrote it
    Native balance, the next nonce to use, and whether the address holds contract code — the three things needed before sending from or to an address. Pass 'token' as well to read an ERC-20 balance for the same address in the same call. Values are read at the latest block, so a reorg can change them. Costs $0.008 USDC per call via x402 on Base.
  • demand_reportFREE, no payment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
  • gas_nowLive gas price on Ethereum, Base, Arbitrum, Optimism or Polygon — in wei and gwei, plus what a plain 21,000-gas transfer would cost in the native token, which is the number you act…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Live gas price on Ethereum, Base, Arbitrum, Optimism or Polygon — in wei and gwei, plus what a plain 21,000-gas transfer would cost in the native token, which is the number you actually budget with. Pass several chains comma-separated to compare where to execute. Call this immediately before sending a transaction: gas moves every block, so the answer is good for seconds, not minutes. Costs $0.005 USDC per call via x402 on Base.
  • request_dataFREE, no payment.No findings

    Why it is in this group

    • The name "request_data" says "request": a word for a change.
    Description, as the server wrote it
    FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just on-chain data — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.
Only reads 2Claude Code: allow
  • token_infoRead an ERC-20's name, symbol, decimals and total supply straight from the contract on the chain you name, and confirm the address actually has code there.1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    Findings

    • Warn

      The input schema at properties.address.examples[0] contains a 42-character base64 string.

      Matched text

      inputSchema.properties.address.examples[0]: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

      What this check looks for
    Description, as the server wrote it
    Read an ERC-20's name, symbol, decimals and total supply straight from the contract on the chain you name, and confirm the address actually has code there. Use before quoting an amount or building a transfer: getting decimals wrong is the classic way to send 1,000,000x the intended value. An address with no code, or a contract that is not an ERC-20, is reported as such and is NOT charged. Costs $0.005 USDC per call via x402 on Base.
  • tx_statusStatus of a transaction by hash: success, failed or still pending, with the block it landed in, sender and recipient, value moved, gas used, the fee actually paid, and how many log…No findings

    Why it is in this group

    • The name "tx_status" says "status": a word for reading.
    Description, as the server wrote it
    Status of a transaction by hash: success, failed or still pending, with the block it landed in, sender and recipient, value moved, gas used, the fee actually paid, and how many logs it emitted. Use to confirm an action you took really settled rather than assuming it did. An unknown hash is reported as not_found and is NOT charged. Costs $0.005 USDC per call via x402 on Base.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http onchain-toolkit https://onchain-toolkit.bowling-anthony.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__onchain-toolkit__token_info",
      "mcp__onchain-toolkit__tx_status"
    ],
    "ask": [
      "mcp__onchain-toolkit__request_data",
      "mcp__onchain-toolkit__demand_report",
      "mcp__onchain-toolkit__gas_now",
      "mcp__onchain-toolkit__address_info"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as onchain-toolkit. Review it before you use it.