Server Details
Free, keyless MCP server with 50 read-only blockchain tools for Bitcoin, Ethereum, and Mezo. No installation, no API key required -- just add the URL to your MCP client and start querying balances, transactions, blocks, ENS names, ERC-20 tokens, smart contracts, and more. Runs on Cloudflare's global edge network via Streamable HTTP. All tools are strictly read-only and stateless.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
13 toolseth_callInspect
Execute a read-only smart contract call on Ethereum mainnet. Returns the hex-encoded return data. Use this to read contract state without sending a transaction.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Contract address | |
| data | Yes | ABI-encoded function call data | |
| from | No | Sender address (optional, for context) | |
| block | No | Block to query (default: latest) |
eth_decode_calldataInspect
Decode raw calldata into function name and typed arguments using a provided ABI on Ethereum mainnet. Pure computation — no RPC call needed. Pass the hex calldata from a transaction input or eth_call.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| calldata | Yes | Raw calldata (0x-prefixed hex) |
eth_decode_logInspect
Decode a raw event log (topics + data) into named fields using a provided ABI on Ethereum mainnet. Pure computation — no RPC call needed. Pass topics and data from a transaction receipt log entry.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| data | Yes | Log data field (0x-prefixed hex, ABI-encoded non-indexed event parameters) | |
| topics | Yes | Log topics array. topics[0] is the event signature hash (keccak256 of the event signature) |
eth_decode_returnInspect
Decode raw return data from an eth_call into typed values using a provided ABI and function name on Ethereum mainnet. Pure computation — no RPC call needed.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| data | Yes | Raw return data (0x-prefixed hex) | |
| function_name | Yes | Name of the function whose output types to decode against |
eth_decode_revertInspect
Decode raw EVM revert data from a failed transaction or eth_call on Ethereum mainnet. Handles Error(string) reverts, Panic(uint256) assertions, custom Solidity errors (requires ABI), and silent reverts. Pure computation — no RPC call needed. Pass the hex revert data from a transaction receipt or eth_call error response.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | No | Contract ABI for decoding custom errors. Pass as a JSON array of error definitions (or as a JSON-encoded string of that array). Only needed for custom errors beyond the built-in Error(string) and Panic(uint256). | |
| revert_data | Yes | Raw revert data as hex (0x-prefixed). Use "0x" or empty string for a silent revert. |
eth_encode_calldataInspect
Encode a function call into ABI-encoded calldata hex. Accepts either a human-readable function signature (e.g. 'transfer(address to, uint256 amount)') or a full ABI JSON array plus function name. Pass uint/int values as decimal strings to avoid JS number precision loss. Pure computation — no RPC call needed.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | No | Full ABI as a JSON array (or JSON-encoded string). Use with function_name. | |
| args | No | Arguments array. Pass uint/int values as decimal or hex strings for precision. | |
| signature | No | Human-readable function signature, e.g. 'transfer(address to, uint256 amount)'. Use instead of abi+function_name. | |
| function_name | No | Function name — required when using abi instead of signature |
eth_multicallInspect
Batch multiple read-only contract calls into a single RPC round trip via Multicall3 on Ethereum mainnet (0xcA11bde05977b3631167028862bE2a173976CA11). Returns success status and raw return data for each call. Use allowFailure=true to prevent one failed call from aborting the whole batch.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | Array of calls to batch (at least 1) |
mezo_callInspect
Execute a read-only smart contract call on Mezo. Returns the hex-encoded return data. Use this to read contract state without sending a transaction.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Contract address | |
| data | Yes | ABI-encoded function call data | |
| from | No | Sender address (optional, for context) | |
| block | No | Block to query (default: latest) |
mezo_decode_calldataInspect
Decode raw calldata into function name and typed arguments using a provided ABI on Mezo. Pure computation — no RPC call needed. Pass the hex calldata from a transaction input or eth_call.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| calldata | Yes | Raw calldata (0x-prefixed hex) |
mezo_decode_logInspect
Decode a raw event log (topics + data) into named fields using a provided ABI on Mezo. Pure computation — no RPC call needed. Pass topics and data from a transaction receipt log entry.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| data | Yes | Log data field (0x-prefixed hex, ABI-encoded non-indexed event parameters) | |
| topics | Yes | Log topics array. topics[0] is the event signature hash (keccak256 of the event signature) |
mezo_decode_returnInspect
Decode raw return data from an eth_call into typed values using a provided ABI and function name on Mezo. Pure computation — no RPC call needed.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | Yes | Contract ABI as a JSON array of ABI items, or a JSON-encoded string of that array | |
| data | Yes | Raw return data (0x-prefixed hex) | |
| function_name | Yes | Name of the function whose output types to decode against |
mezo_decode_revertInspect
Decode raw EVM revert data from a failed transaction or mezo_call on Mezo. Handles Error(string) reverts, Panic(uint256) assertions, custom Solidity errors (requires ABI), and silent reverts. Pure computation — no RPC call needed. Pass the hex revert data from a transaction receipt or eth_call error response.
| Name | Required | Description | Default |
|---|---|---|---|
| abi | No | Contract ABI for decoding custom errors. Pass as a JSON array of error definitions (or as a JSON-encoded string of that array). Only needed for custom errors beyond the built-in Error(string) and Panic(uint256). | |
| revert_data | Yes | Raw revert data as hex (0x-prefixed). Use "0x" or empty string for a silent revert. |
mezo_multicallInspect
Batch multiple read-only contract calls into a single RPC round trip via Multicall3 on Mezo (0xcA11bde05977b3631167028862bE2a173976CA11). Returns success status and raw return data for each call. Use allowFailure=true to prevent one failed call from aborting the whole batch.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | Array of calls to batch (at least 1) |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!