MACH Base

What MACH Base MCP server does

MACH Base MCP server gives AI agents access to live Base mainnet data through MCP tools. It is intended for agents that need current network, wallet, token, contract, block, or transaction information.

The service includes 16 paid tools. Most calls cost $0.005 USDC through x402; the transaction lookup tool costs $0.008 USDC.

How it works

Agents connect to the endpoint at https://api.mach.gallery/mcp using Streamable HTTP MCP. They select a tool and provide the relevant Base address, token address, transaction hash, block identifier, event filters, or contract call parameters. The service queries live Base mainnet data and returns the requested result.

Payment is handled per call with USDC through x402. The material does not specify a wallet setup, payment client configuration, network for settlement, or retry behavior, so those details should be verified before deployment.

Setup and configuration

Configure an MCP-compatible client to use the Streamable HTTP endpoint:

https://api.mach.gallery/mcp

No environment variables, API keys, user account, or subscription are listed as required. The calling environment must still support the service’s x402 payment flow and provide whatever payment details that flow requires. Exact client configuration varies by MCP host and is not provided here.

Tools and capabilities

The MACH Base MCP server provides tools for:

• Reading the current Base block number and gas price.
• Checking native ETH balances, ERC-20 balances, nonces, and ERC-20 allowances.
• Determining whether an address contains deployed contract bytecode.
• Looking up transactions, receipts, confirmation depth, and block headers with transaction hashes.
• Running read-only eth_call requests at a selected block tag.
• Filtering bounded contract logs by address, topics, and block range.
• Reading native ETH and up to 10 caller-supplied ERC-20 balances in one wallet snapshot.
• Reading ERC-20 or ERC-721 total supply.
• Inspecting contract bytecode, best-effort token metadata, and common token interfaces.
• Querying bounded ERC-20 Transfer events with optional sender and recipient filters.

The wallet and token tools operate on Base addresses and contracts. Event and log queries are bounded by the filters supplied to the tool, including block ranges where supported.

Limitations and notes

MACH Base MCP server is described as a data access service for Base mainnet.

Every tool call is paid, so automated workflows should account for per-request USDC costs. Most calls have the same listed price, while base_transaction costs more.

Results are live reads at request time. Contract metadata is best effort, and base_contract_info should not be treated as a complete token verification or indexing service.