@cryptoapis-io/mcp-prepare-transactions
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRYPTOAPIS_API_KEY | Yes | Crypto APIs API key. Required for all requests. Can be provided via --api-key CLI argument instead. |
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 |
|---|---|
| prepare_transactions_evmA | Build unsigned EVM transactions ready for signing. Returns the raw unsigned transaction hex and fee details. After preparing, use a signing tool (e.g. evm_sign) to sign locally, then broadcast via broadcast_signed_transaction. Actions: • prepare-transaction-from-address: Build an unsigned native coin transfer (e.g. ETH, BNB) • prepare-fungible-token-transfer: Build an unsigned ERC-20 token transfer • prepare-nft-transfer: Build an unsigned ERC-721 NFT transfer Credits by action (source: OpenAPI): • prepare-fungible-token-transfer: 24 • prepare-nft-transfer: 24 • prepare-transaction-from-address: 24 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 |
|---|---|
| prepare-evm-transaction | Build an unsigned EVM transaction ready for signing |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-chains | Supported blockchains, networks, and actions for prepare-transactions |
TDQS
Scored across 2 tools
The two tools are completely distinct: one prepares unsigned EVM transactions with clear sub-actions, the other provides static system reference information. There is no overlap or ambiguity between them.
Both tool names use snake_case and are descriptive, but the pattern differs slightly: 'prepare_transactions_evm' is verb_noun while 'system_info' is noun_noun. This is a minor deviation but not confusing given the small set.
With only 2 tools, the server feels slightly thin for a general-purpose service, but the main tool (prepare_transactions_evm) bundles multiple transaction types, and system_info serves as a useful reference. The count is acceptable for a focused transaction preparation server.
The server covers the essential EVM transaction preparation scenarios: native transfers, ERC-20 transfers, and NFT transfers. It lacks more advanced options like contract calls or multi-sig transactions, but for a prepare-only tool, the core lifecycle is well covered.