_ registry / mcp streamable-http · checked 6h ago

base-intel

https://base.datakoot.com

Registry code: b290b8122e56c9f7

api record

Base Intel: read-only on-chain data for the Base network - address snapshots (ETH and USDC balance, tx count, contract check), ERC-20 token metadata and balances, live gas price, and transaction status. Have a wallet address? Call address_report first for a one-call overview, then token_balance for a specific ERC-20.

endpoint
https://base.datakoot.com/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 base-intel live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is base-intel free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does base-intel have?
5 tools: address_report, tx_status, gas_now, token_info, token_balance.
Is base-intel 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.6%

90 days 98.8%· all time 98.8%

latency
153ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 515 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain wallets & balances
used for
  • get a base address snapshot
  • get erc-20 token balance on base
  • check base transaction status
  • get base gas price
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open2 auth-required 2 never probed 3 of 5 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.

  • gas_now reads open 23h ago

    Current gas price on the Base network (Coinbase's Ethereum L2), in gwei and wei, read live from a Base RPC node. Use before sending a Base transaction or estimating its cost. Takes no input.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • token_info reads auth-required 14h ago

    ERC-20 token metadata on Base, read on-chain: name, symbol, decimals, and total supply, plus whether the address really behaves like an ERC-20. Use it to verify a token contract before trusting or displaying it. Input: the token contract address (0x + 40 hex).

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "ERC-20 contract address on Base: 0x followed by 40 hex characters."
    }
  }
}
    arguments 12 lines
  • token_balance reads auth-required 23h ago

    How much of an ERC-20 token a wallet holds on Base, returned both human-formatted (using the token's decimals) and raw. Pass the token contract address and the holder address, both 0x + 40 hex. Example: USDC 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token",
    "address"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "ERC-20 contract address on Base: 0x followed by 40 hex characters."
    },
    "address": {
      "type": "string",
      "description": "Wallet address whose balance to read: 0x followed by 40 hex characters."
    }
  }
}
    arguments 17 lines
  • address_report reads unknown never probed

    One-call snapshot of any Base address: ETH balance, USDC balance, transaction count, and whether it is a smart contract or a regular wallet. Use it to sanity-check a counterparty or a payment address before sending funds. Input: a 0x address.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "0x address on Base"
    }
  }
}
    arguments 12 lines
  • tx_status reads unknown 23h ago

    Look up a Base transaction by hash and report whether it is pending, succeeded, or failed, with from, to, value, block number, and gas used. Use it to confirm a payment or contract call landed. Input: the transaction hash (0x + 64 hex; the 0x is optional).

    mcp-tool

    {
  "type": "object",
  "required": [
    "hash"
  ],
  "properties": {
    "hash": {
      "type": "string",
      "description": "Transaction hash, 0x followed by 64 hex characters (the 0x prefix is optional)."
    }
  }
}
    arguments 12 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 b290b8122e56c9f7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b290b8122e56c9f7/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/b290b8122e56c9f7/badge.svg)](https://brick.blue/agent/b290b8122e56c9f7?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
90%

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.

_ also on datakoot.com 10 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

2 more sit on this domain. All of them.