_ registry / mcp streamable-http · checked 38m ago

com.mcpscores/onchain-toolkit

https://onchain-toolkit.bowling-anthony.workers.dev

Registry code: a82b49d0b5d3a72e

api record

On-chain facts for the seconds before you transact: live gas across Ethereum, Base, Arbitrum, Optimism and Polygon; an ERC-20's decimals and symbol read from the contract; whether a transaction actually succeeded; and an address's balance and next nonce. Tool calls are x402-paid in USDC on Base — send the base64 X-PAYMENT header on this POST /mcp request (or params._meta['x402/payment']). gas_now, token_info and tx_status cost $0.005; address_info $0.008. An unpaid call returns a PaymentRequired result and settles nothing; initialize, ping and tools/list are free, as are request_data and…

endpoint
https://onchain-toolkit.bowling-anthony.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.mcpscores/onchain-toolkit live?
Yes — it answered the hub's last check (checked 38m ago). It answered 99% of checks over the last 30 days.
Is com.mcpscores/onchain-toolkit free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.mcpscores/onchain-toolkit have?
6 tools: demand_report, gas_now, token_info, tx_status, address_info, request_data.
Is com.mcpscores/onchain-toolkit safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.1%· all time 99.3%

latency
145ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 220 checks · signed record
_ what it is for
used for
  • get live gas prices
  • read erc-20 token info
  • check transaction status
  • get address balance and nonce
takes → gives
text → data
tools
5 reads1 changes data
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ paid on base 30 days

Read off the chain, not reported by anybody: USDC settlements into the address this operator's priced doors name, recognised by the shape of an x402 payment. The operator paying itself is left out, and fewer than three real payers counts as none. This address also stands behind 12 other origins: the figure is the gateway's, not this listing's alone. How it is counted.

payers
8

distinct, not the operator

settlements
14

last 2026-10-04

received
0.101 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • demand_report reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "string",
          "examples": [
            "30"
          ],
          "description": "Window in days, default 30, max 90."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • gas_now reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "chain": {
          "type": "string",
          "examples": [
            "base"
          ],
          "description": "One or more of ethereum, base, arbitrum, optimism, polygon — comma-separated, e.g. 'base,ethereum'. Defaults to base."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • token_info reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "examples": [
            "base"
          ],
          "description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
        },
        "address": {
          "type": "string",
          "examples": [
            "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
          ],
          "description": "0x-prefixed 20-byte contract address."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • tx_status reads unknown 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "hash"
      ],
      "properties": {
        "hash": {
          "type": "string",
          "examples": [
            "0x08001b920b214572ff2e7a4fc4560bafa717619b00b91561425ef6a325fdfedb"
          ],
          "description": "0x-prefixed 32-byte transaction hash."
        },
        "chain": {
          "type": "string",
          "examples": [
            "base"
          ],
          "description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • address_info reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "examples": [
            "base"
          ],
          "description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
        },
        "token": {
          "type": "string",
          "examples": [
            "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
          ],
          "description": "Optional ERC-20 contract address to also report that token's balance."
        },
        "address": {
          "type": "string",
          "examples": [
            "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
          ],
          "description": "0x-prefixed 20-byte address."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • request_data changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "examples": [
            "live electricity spot prices by ZIP"
          ],
          "description": "What you are looking for."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a82b49d0b5d3a72e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a82b49d0b5d3a72e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a82b49d0b5d3a72e/badge.svg)](https://brick.blue/agent/a82b49d0b5d3a72e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.