Skip to main content
Glama
CryptoAPIs-io

@cryptoapis-io/mcp-prepare-transactions

Official
by CryptoAPIs-io
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

@cryptoapis-io/mcp-prepare-transactions

MCP server for Crypto APIs Prepare Transactions product. Build unsigned EVM transactions for native coin transfers, fungible token transfers, and NFT transfers.

API Version: Compatible with Crypto APIs version 2024-12-12

Features

  • Prepare native coin transfer transactions (from address)

  • Prepare fungible token (ERC-20) transfer transactions

  • Prepare NFT (ERC-721) transfer transactions

  • Returns unsigned transaction hex ready for signing with @cryptoapis-io/mcp-signer

Related MCP server: @cryptoapis-io/mcp-signer

Prerequisites

Installation

npm install @cryptoapis-io/mcp-prepare-transactions

Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp

Usage

# Run with API key
npx @cryptoapis-io/mcp-prepare-transactions --api-key YOUR_API_KEY

# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-prepare-transactions

# HTTP transport
npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000 --api-key YOUR_API_KEY

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "cryptoapis-prepare-transactions": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-prepare-transactions"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "cryptoapis-prepare-transactions": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-prepare-transactions"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}

MCP Inspector

npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-prepare-transactions --api-key YOUR_API_KEY

n8n

  1. Start the server in HTTP mode:

    npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000 --api-key YOUR_API_KEY

  2. In your n8n workflow, add an AI Agent node

  3. Under Tools, add an MCP Client Tool and set the URL to http://localhost:3000/mcp

All servers default to port 3000. Use --port to assign different ports when running multiple servers.

Available Tools

prepare_transactions_evm

Prepare unsigned EVM transactions.

Action

Description

prepare-transaction-from-address

Prepare a native coin transfer from an address

prepare-fungible-token-transfer

Prepare an ERC-20 token transfer

prepare-nft-transfer

Prepare an ERC-721 NFT transfer

CLI Arguments

Argument

Description

Default

--api-key

Crypto APIs API key

CRYPTOAPIS_API_KEY env var

--transport

Transport type: stdio or http

stdio

--host

HTTP host

0.0.0.0

--port

HTTP port

3000

--path

HTTP path

/mcp

--stateless

Enable stateless HTTP mode

false

HTTP API Key Modes

When using HTTP transport, the server supports two API key modes:

  • With --api-key: The key is used for all requests. x-api-key request headers are ignored.

  • Without --api-key: Each request must include an x-api-key header with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.

# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000
# Clients send x-api-key header with each request

Stdio transport always requires an API key at startup.

Important: API Key Required

Warning: Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.

Remote MCP Server

Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.

License

MIT

Available Tools

2 tools
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
valueNoAmount in native coin's smallest unit, e.g. wei (required for prepare-transaction-from-address)
actionYesAction to perform
amountNoToken amount to transfer (required for prepare-fungible-token-transfer)
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
tokenIdNoNFT token ID (required for prepare-nft-transfer)
gasLimitNoCustom gas limit override (prepare-transaction-from-address only; auto-estimated if omitted)
gasPriceNoCustom gas price in wei (prepare-transaction-from-address only; auto-estimated if omitted)
toAddressNoRecipient address (required for all actions)
blockchainYesBlockchain protocol
fromAddressNoSender address (required for all actions)
contractAddressNoToken contract address (required for prepare-fungible-token-transfer and prepare-nft-transfer)

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full responsibility for disclosure. It reveals that the tool returns the raw unsigned transaction hex and fee details, and it implies the operation has no on-chain side effects ('ready for signing'). It also adds credit cost details, which is useful context. It does not cover all potential behaviors (e.g., authentication, rate limits), but it covers the essential nature of the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: it starts with a clear one-sentence overview, then lists the three actions with brief explanations, and finally includes credit information. It is concise enough for the complexity it covers, though the credit section could be trimmed if not essential, but it does contribute operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 12 parameters and no output schema, yet the description gives sufficient context: it names the three actions, describes the expected output (transaction hex and fee details), and outlines the follow-up steps for signing and broadcasting. It does not provide examples or error handling details, but for correct invocation it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides descriptions for 100% of the parameters, including which actions they apply to. The tool description adds value by explaining what each action does, but it does not add meaning for individual parameters beyond the schema. Given the high schema coverage, this baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Build unsigned EVM transactions ready for signing.' It lists three specific actions (native transfer, ERC-20 transfer, NFT transfer), which distinguishes it from downstream signing and broadcasting tools. The mention of the prepare-sign-broadcast workflow further differentiates its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool: before signing locally via a tool like evm_sign, and before broadcasting via broadcast_signed_transaction. It gives a clear sequential workflow but does not explicitly state when not to use it or name alternative preparation tools, so it falls slightly short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYesReference topic to retrieve
contextNoOptional context for the request - echoed back in response

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the transparency burden. It explicitly discloses that no API call is made and no credits are consumed, and it details what each action returns. It does not mention response format or potential side effects, but for a pure documentation tool this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear one-line summary followed by a bulleted list of actions. Each bullet is concise and informative, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a documentation tool with one enum parameter and no output schema, the description is fully complete. It covers all available actions, their content, and the tool's non-executing nature, leaving no ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, but the description adds significant meaning by detailing what each enum action returns (e.g., blockchains -> supported chains, errors -> error table, credits -> cost structure). This goes beyond the schema's generic description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is 'CryptoAPIs reference documentation' and enumerates the exact topics (blockchains, errors, credits, callbacks, limits). This distinguishes it from the sibling tool prepare_transactions_evm, which handles transaction preparation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving reference information and explicitly notes 'no API call, no credits consumed', making it clear this is a documentation tool. However, it does not explicitly state when to use it over alternatives or provide exclusions, only relying on the obvious contrast with the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.3.0
    • First observedprepare_transactions_evm
    • First observedsystem_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CryptoAPIs-io/cryptoapis-mcp-prepare-transactions'

If you have feedback or need assistance with the MCP directory API, please join our Discord server