MCP server for building unsigned transactions on multiple blockchains via Crypto APIs
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cryptoapis-prepare-transactions": {
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
},
"args": [
"-y",
"@cryptoapis-io/mcp-prepare-transactions"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Crypto APIs Prepare Transactions product. Build unsigned EVM transactions for native coin transfers, fungible token transfers, and NFT transfers.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@cryptoapis-io/mcp-prepare-transactions' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @cryptoapis-io/mcp-prepare-transactions against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol (MCP) server that provides AI assistants with direct access to the Spreedly payments API. Enables LLMs to manage gateways, process transactions, tokenize payment methods, and more, through structured, validated tool calls.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
Model Context Protocol for Actual Budget API
MCP Security Weekly
Get CVE alerts and security updates for io.github.CryptoAPIs-io/mcp-prepare-transactions and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
@cryptoapis-io/mcp-signernpm install @cryptoapis-io/mcp-prepare-transactions
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# 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
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"
}
}
}
}
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"
}
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-prepare-transactions --api-key YOUR_API_KEY
npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000 --api-key YOUR_API_KEY
http://localhost:3000/mcpAll servers default to port 3000. Use
--portto assign different ports when running multiple servers.
prepare_transactions_evmPrepare 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 |
| 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 |
When using HTTP transport, the server supports two API key modes:
--api-key: The key is used for all requests. x-api-key request headers are ignored.--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.
Warning: Making requests without a valid API