@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. |
| prepare_transactions_tezosA | Build unsigned Tezos operations ready for signing. Returns the forged (unsigned) operation bytes and fee details. After preparing, sign locally and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native XTZ transfer • fa1-2-tokens: Build an unsigned FA1.2 token transfer • fa2-tokens: Build an unsigned FA2 token transfer Credits by action (source: OpenAPI): • fa1-2-tokens: 104 • fa2-tokens: 104 • native-coins: 78 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| prepare_transactions_solanaA | Build unsigned Solana transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native SOL transfer • spl-tokens: Build an unsigned SPL token transfer Credits by action (source: OpenAPI): • native-coins: 180 • spl-tokens: 240 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| prepare_transactions_kaspaA | Build unsigned Kaspa transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (kaspa_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native KAS transfer, supporting multiple recipients in one transaction Credits by action (source: OpenAPI): • native-coins: 60 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| prepare_transactions_xrpA | Build unsigned XRP transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (xrp_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native XRP transfer Credits by action (source: OpenAPI): • native-coins: 60 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| prepare_transactions_utxoA | Build unsigned UTXO transactions ready for signing (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). Returns the unsigned transaction and fee details. After preparing, sign locally (utxo_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native coin transfer, supporting multiple recipients in one transaction. Requires either feePriority or exactFee. Credits by action (source: OpenAPI): • native-coins: 530 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| prepare_transactions_tronA | Build unsigned Tron transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (tron_sign) and broadcast via broadcast_signed_transaction. These are Tron's dedicated prepare-transactions endpoints, distinct from the generic EVM ones used for other chains. Actions: • native-coins: Build an unsigned native TRX transfer • trc20-tokens: Build an unsigned TRC-20 token transfer • non-fungible-tokens: Build an unsigned TRC-721/TRC-1155 NFT transfer Credits by action (source: OpenAPI): • native-coins: 90 • non-fungible-tokens: 128 • trc20-tokens: 120 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 8 tools
Each tool targets a specific blockchain family (Tron, Tezos, Solana, Kaspa, XRP, UTXO, EVM) with clear distinctions, and descriptions explicitly differentiate dedicated chain endpoints from generic EVM. The system_info tool is clearly separate as a reference resource.
Seven of eight tools follow the consistent snake_case pattern prepare_transactions_<chain>, but system_info breaks the pattern as a non-action reference tool. The deviation is minor and readable.
Eight tools are well-scoped for preparing transactions across major blockchain families, with one tool per chain family plus a reference tool. No redundancy or excessive granularity.
The set covers native, token, and NFT transfers for most listed chains, but some chains lack token support (e.g., XRP, Kaspa only native) and possible chains (e.g., Cosmos, Algorand) are missing. Within the prepare-only scope, coverage is strong.