# BRAINIAC Base Chain Data [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://www.brainiac.software/mcp/chain-data  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/brainiac-base-chain-data

## Description
Base Chain Data: 16 pay-per-call MCP tools for agents (x402 USDC on Base, no API key). Base Chain Data tools for AI agents: get network information; get latest block; get block by number or hash; get block transactions; get transaction receipt; search contract event logs; and 10 more.

## Tools
Capabilities this server exposes over MCP:

- **chain-data_network-info** — Retrieve Base Mainnet chain ID and network information from the public JSON-RPC endpoint when you need Base chain data. Call with none. Returns network, latestBlockNumber, and source (network includes chainId, chainName, rpcEndpoint). Base Mainnet only. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, network, latestBlockNumber, source, Get network information, network info, Base Mainnet, Base Chain Data.
- **chain-data_block_latest** — Retrieve the latest block information from Base Mainnet using the public JSON-RPC endpoint when you need Base chain data. Call with none. Returns block, chainId, and source (block includes number, hash, parentHash, timestamp, transactions, baseFeePerGas, gasLimit, gasUsed). Base Mainnet only. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, block, chainId, source, Get latest block, latest, Base Mainnet, Base Chain Data.
- **chain-data_block_get** — Retrieve a specific block by number or hash from Base Mainnet when you need Base chain data. Supports optional full transaction details. Call with optional blockNumber, blockHash, fullTransactions. Returns block, chainId, and source (block includes number, hash, parentHash, timestamp, transactions, baseFeePerGas, gasLimit, gasUsed). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, blockNumber, blockHash, fullTransactions, block, chainId, source, Get block by number or hash, get, Base Mainnet.
- **chain-data_block_transactions** — Retrieve all transactions included in a specific block by number or hash from Base Mainnet when you need Base chain data. Call with optional blockNumber, blockHash. Returns transactions, blockHash, blockNumber, chainId, and source (transactions includes hash, nonce, blockHash, blockNumber, transactionIndex, from, to, value). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, blockNumber, blockHash, transactions, chainId, source, Get block transactions, Base Mainnet.
- **chain-data_transaction_receipt** — Retrieve the receipt and status for a specific transaction on Base Mainnet, including logs and gas used when you need Base chain data. Call with txHash. Returns receipt, txHash, and source (source includes url, status). Base Mainnet only. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, txHash, receipt, source, Get transaction receipt, Base Mainnet, Base Chain Data, chain data.
- **chain-data_logs_search** — Search for contract event logs on Base Mainnet with filters for block range, address, and topics when you need Base chain data. Limited to 1000 results per request. Call with optional fromBlock, toBlock, blockHash, address, topics, limit. Returns logs and source (source includes url, status, error). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, fromBlock, toBlock, blockHash, address, topics, limit, logs, source, Search contract event logs, search, Base Mainnet.
- **chain-data_contract_code** — Retrieve the bytecode of a smart contract on Base Mainnet at a specific address and optional block number when you need Base chain data. Call with address (a 0x-prefixed 40-hex address); optional blockNumber. Returns address, code, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, address, blockNumber, code, chainId, source, Get contract bytecode, Base Mainnet.
- **chain-data_contract_read** — Execute a read-only call to a smart contract on Base Mainnet using eth_call when you need Base chain data. Returns the result without submitting a transaction. Call with address and data; optional blockNumber. Returns address, data, result, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, address, data, blockNumber, result, chainId, source, Execute read-only contract call, read, Base Mainnet.
- **chain-data_gas_estimate** — Estimate the gas required for a transaction on Base Mainnet using eth_estimateGas when you need Base chain data. Call with optional from, to, value, data. Returns estimate, chainId, and source (source includes url, status). Base Mainnet only. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, from, value, data, estimate, chainId, source, Estimate gas for transaction, Base Mainnet.
- **chain-data_gas_fee-history** — Retrieve the fee history for Base Mainnet blocks, including base fees and reward percentiles when you need Base chain data. Supports EIP-1559. Call with optional blockCount, newestBlock, rewardPercentiles. Returns history, chainId, and source (history includes baseFeePerGas, gasUsedRatio, oldestBlock, reward). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, blockCount, newestBlock, rewardPercentiles, history, chainId, source, Get fee history, fee history, Base Mainnet.
- **chain-data_address_native-balance** — Retrieve the native ETH balance of a Base Mainnet address from the public JSON-RPC endpoint when you need Base chain data. Call with address (a 0x-prefixed 40-hex address); optional blockNumber. Returns address, balance, balanceDecimal, blockNumber, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, address, blockNumber, balance, balanceDecimal, chainId, source, Get native ETH balance, native balance, Base Mainnet.
- **chain-data_token_erc20-balance** — Retrieve the ERC-20 token balance of a wallet for a specified token contract on Base Mainnet using eth_call when you need Base chain data. Call with walletAddress and tokenAddress; optional blockNumber. Returns walletAddress, tokenAddress, balance, balanceDecimal, blockNumber, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, walletAddress, tokenAddress, blockNumber, balance, balanceDecimal, chainId, source, Get ERC-20 balance, erc20 balance, Base Mainnet.
- **chain-data_token_erc20-total-supply** — Retrieve the total supply of an ERC-20 token on Base Mainnet using eth_call when you need Base chain data. Call with tokenAddress (a 0x-prefixed 40-hex address); optional blockNumber. Returns tokenAddress, totalSupply, totalSupplyDecimal, blockNumber, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, tokenAddress, blockNumber, totalSupply, totalSupplyDecimal, chainId, source, Get ERC-20 total supply, erc20 total supply, Base Mainnet.
- **chain-data_token_metadata** — Retrieve ERC-20 name, symbol, decimals, and total supply for a token on Base Mainnet where supported when you need Base chain data. Call with tokenAddress (a 0x-prefixed 40-hex address); optional blockNumber. Returns tokenAddress, name, symbol, decimals, totalSupply, totalSupplyDecimal, blockNumber, and chainId. Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, tokenAddress, blockNumber, name, symbol, decimals, totalSupply, totalSupplyDecimal, chainId, Get token metadata, metadata, Base Mainnet.
- **chain-data_token_erc20-transfers** — Retrieve ERC-20 Transfer events for a token contract or wallet on Base Mainnet over a bounded block range when you need Base chain data. Call with optional tokenAddress, walletAddress, fromBlock, toBlock, limit. Returns transfers, fromBlock, toBlock, and source (source includes url, status, error). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, tokenAddress, walletAddress, fromBlock, toBlock, limit, transfers, source, Get ERC-20 transfers, erc20 transfers, Base Mainnet.
- **chain-data_address_nonce** — Retrieve the transaction nonce for a Base Mainnet address from the public JSON-RPC endpoint when you need Base chain data. Call with address (a 0x-prefixed 40-hex address); optional blockNumber. Returns address, nonce, nonceHex, blockNumber, chainId, and source (source includes url, status). Base Mainnet only. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: when you need Base chain data, address, blockNumber, nonce, nonceHex, chainId, source, Get address nonce, Base Mainnet.
- **chain-data_gas_current** — Current Base gas fees in gwei, plus a USD estimate for a simple 21,000-gas transfer, from the public Base JSON-RPC fee history and a public ETH/USD source. Call with no body. Returns base fee, slow/standard/fast priority fees, the 21,000 gas estimate in ETH and USD, the ETH/USD source, and as-of time. This is a current-fee snapshot, not a guaranteed inclusion price. HTTP 200 with status complete, partial, or failed is charged in full. Cache freshness is stated in the body (target 15 seconds). Keywords: base gas, gas oracle, gas price, gwei, EIP-1559, base fee, priority fee, simple transfer, 21000 gas, USD estimate, ETH/USD, current fees, Base mainnet.
- **chain-data_gas_evm** — Current EIP-1559 gas snapshot for Ethereum, Base, Arbitrum, Optimism, and Polygon from public RPC: base fee, slow/standard/fast priority, and a simple-transfer USD estimate using Chainlink. This is a current-fee snapshot, not a guaranteed inclusion price. HTTP 200 with status complete, partial, or failed is charged in full Call when you need this official data before acting Call when you need this official data before acting. Keywords: ethereum gas, evm gas oracle, arbitrum gas, optimism gas, polygon gas, EIP-1559.
- **chain-data_ens_resolve** — Resolve an ENS or Basename to an address, or an address to a forward-confirmed primary name, from the official ENS registry on Ethereum and the official Basenames resolver on Base. A reverse name is returned only when the forward record matches. Public RPC, no explorer key. HTTP 200 with status complete, partial, or failed is charged in full Call when you need this official data before acting Call when you need this official data before acting. Keywords: ENS resolve, vitalik.eth, Basename, jesse.base.eth, reverse ENS, primary name.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "brainiac-base-chain-data": {
    "url": "https://www.brainiac.software/mcp/chain-data"
  }
}
```

## Documentation

## What BRAINIAC Base Chain Data does

BRAINIAC Base Chain Data exposes blockchain read operations as MCP tools through the hosted endpoint `https://www.brainiac.software/mcp/chain-data`. The primary network is Base Mainnet. Agents can retrieve network details, the latest block, a block by number or hash, transactions in a block, transaction receipts, contract event logs, contract bytecode, and results from read-only contract calls.

The tool set also covers operational data needed by wallets and transaction-building agents. It can estimate gas, retrieve EIP-1559 fee history, report current Base fees, estimate the ETH and USD cost of a simple 21,000-gas transfer, read native ETH balances, obtain address nonces, and query ERC-20 balances, metadata, total supply, and transfer events. An additional gas snapshot covers Ethereum, Base, Arbitrum, Optimism, and Polygon. ENS and Basenames resolution is also available, including forward resolution and forward-confirmed reverse primary names.

## How it works

An MCP client connects to the hosted HTTP endpoint and invokes individual tools with JSON arguments. Most Base queries use the public JSON-RPC endpoint. Contract reads use `eth_call`, gas estimation uses `eth_estimateGas`, and fee-related tools obtain data from public RPC sources. The current-fee tool also uses a public ETH/USD source, while the multi-network gas snapshot uses Chainlink for its simple-transfer USD estimate.

Inputs are generally optional when a tool can use the latest chain state. Block, transaction, contract, wallet, and token queries accept hexadecimal blockchain identifiers and addresses where applicable. Contract addresses must be 0x-prefixed 40-hex addresses. Log searches support block ranges, addresses, topics, and a result limit; each request is limited to 1,000 log results. ERC-20 transfer searches use a bounded block range.

## Setup and configuration

Use the hosted endpoint as the MCP server URL in a compatible MCP client. No API key is required. Calls are paid with x402 USDC on Base. A payment signature by itself does not settle a charge; settlement occurs only when the request returns HTTP 2xx. Successful HTTP 200 responses are charged at the full listed price even when the body reports `complete`, `partial`, or `failed`. HTTP 4xx and 5xx responses are not charged.

No environment variables are needed for the hosted service. Clients and agents must still be configured to provide valid tool arguments and, for paid calls, support the payment flow required by the endpoint.

## Tools and capabilities

- Inspect Base network information and the latest block.
- Retrieve blocks by number or hash, optionally including complete transaction objects.
- List block transactions and fetch transaction receipts with logs and gas usage.
- Search contract logs with block, address, and topic filters.
- Read contract bytecode or execute a read-only `eth_call`.
- Estimate transaction gas and inspect historical or current EIP-1559 fees.
- Query ETH balances, address nonces, ERC-20 balances, metadata, and total supply.
- Find ERC-20 transfer events for a token or wallet.
- Compare current gas conditions across supported EVM networks.
- Resolve ENS names and Basenames with forward-confirmed reverse results.

## Limitations and notes

The standard chain-data queries target Base Mainnet rather than arbitrary networks. Current gas results are snapshots, not guarantees that a transaction will be included at the quoted fee; the Base fee tool states a target freshness of 15 seconds in its response. Token metadata is returned where supported, and log searches cannot return more than 1,000 results per request.

The service is read-oriented. Its contract tool performs read-only calls and the listed operations do not submit transactions or mutate chain state. Payment behavior matters when handling partial or failed HTTP 200 responses because those responses are still charged in full. ENS resolution uses the official ENS registry on Ethereum and the official Basenames resolver on Base, while public RPC access avoids an explorer API key.

_Full upstream README: https://allmcps.com/mcp/brainiac-base-chain-data/readme_

