MCP server for transaction lookup across EVM, UTXO, Solana, XRP, Kaspa via Crypto APIs
MCP server for transaction lookup across EVM, UTXO, Solana, XRP, Kaspa via Crypto APIs
Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (23/23 approved).
12 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Set these up before or after installing:
Environment variable: CRYPTOAPIS_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cryptoapis-io-mcp-transactions-data": {
"env": {
"CRYPTOAPIS_API_KEY": "your-cryptoapis-api-key-here"
},
"args": [
"-y",
"@cryptoapis-io/mcp-transactions-data"
],
"command": "npx"
}
}
}Once installed, try these example prompts and explore these capabilities:
From the project's GitHub README.
MCP server for Crypto APIs Transactions Data product. Look up transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
API Version: Compatible with Crypto APIs version 2024-12-12
npm install @cryptoapis-io/mcp-transactions-data
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# Run with API key
npx @cryptoapis-io/mcp-transactions-data --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-transactions-data
# HTTP transport
npx @cryptoapis-io/mcp-transactions-data --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-transactions-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-transactions-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-transactions-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-transactions-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-transactions-data --api-key YOUR_API_KEY
npx @cryptoapis-io/mcp-transactions-data --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.
transactions_data_utxoUTXO transaction details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
| Action | Description |
|---|---|
get-transaction-details | Get transaction details by hash |
get-raw-transaction-data | Get raw transaction data by hash |
transactions_data_evmEVM transaction details (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).
| Action | Description |
|---|---|
get-transaction-details | Get transaction details by hash |
list-internal-transactions | List internal transactions by hash |
list-token-transfers | List token transfers by hash |
list-logs | List event logs by hash |
transactions_data_solanaSolana transaction details (mainnet, devnet).
| Parameter | Description |
|---|---|
network | Network (mainnet, devnet) |
transactionHash | Transaction signature |
transactions_data_xrpXRP transaction details (mainnet, testnet).
| Parameter | Description |
|---|---|
network | Network (mainnet, testnet) |
transactionHash | Transaction hash |
transactions_data_kaspaKaspa transaction details (mainnet).
| Parameter | Description |
|---|---|
network | Network (mainnet) |
transactionId | Transaction ID |
| 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-transactions-data --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 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.
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.
MIT
Be the first to review this server!
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.
by Taylorwilsdon · Productivity
Control Gmail, Calendar, Docs, Sheets, Drive, and more from your AI