CryptoAPIs Contracts MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Bearer token that HTTP callers must send in Authorization header. Required when binding HTTP server to non-loopback addresses. Optional otherwise. | |
| CRYPTOAPIS_API_KEY | Yes | Crypto APIs API key. Required for stdio transport and for HTTP transport if --api-key is not provided. Can also be passed via --api-key CLI argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evm_contract_dataA | Get EVM contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details (name, symbol, standard, decimals, totalSupply) by contract address Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: binance-smart-chain 75, ethereum 30, ethereum-classic 39 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| solana_contract_dataB | Get Solana contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details by contract address Networks: mainnet, devnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: 75 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| system_infoA | CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| read-contract | Read data from a deployed smart contract |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-chains | Supported blockchains, networks, and actions for contract data queries |
TDQS
Scored across 3 tools
The tools are clearly separated by blockchain ecosystem: evm_contract_data, solana_contract_data, and system_info. The first two target different chains, and system_info is explicitly a reference tool with no API call, so an agent can easily select the correct tool.
All tool names use consistent snake_case and are descriptive. The two chain-specific tools follow the same [chain]_contract_data pattern, while system_info remains readable and consistent with the overall naming style.
Three tools is a small but workable set for a focused contract-data server. The two chain-specific tools earn their place, though the server feels slightly under-scoped for a product named 'Contracts MCP'.
The surface covers token details for EVM and Solana contracts and includes useful reference documentation. However, it lacks other contract-related operations such as ABI retrieval, event logs, or transfer queries, leaving notable gaps for broader contract analysis.