All servers · Crypto & blockchain
Base Intel MCP
com.datakoot/base-onchain-wallet-tokens · v2.1.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
Connect
streamable-http · https://base.datakoot.com/mcp
claude mcp add --transport http base-onchain-wallet-tokens https://base.datakoot.com/mcp{
"mcpServers": {
"base-onchain-wallet-tokens": {
"url": "https://base.datakoot.com/mcp"
}
}
}Tools as reported by the server
address_reportOne-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.token_infoERC-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).token_balanceHow 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.gas_nowCurrent 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.tx_statusLook 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).
Repository · JSON · Text for agents · Registry updated 2026-09-02