Mcp Address History
Fetch full on-chain transaction and token history for EVM and UTXO addresses through Crypto APIs via MCP.
Overview
CryptoAPIs MCP Address History is a Build-phase MCP server that returns EVM and UTXO address transaction and token history via Crypto APIs.
What is this MCP server?
- MCP server @cryptoapis-io/mcp-address-history on npm with stdio transport
- Surfaces transaction and token transfer history for EVM and UTXO address types
- Authenticated with CRYPTOAPIS_API_KEY secret
- Version 0.3.0 registered on Model Context Protocol server schema
- Focused scope: address history rather than a full multi-chain wallet suite
- Package version 0.3.0 (@cryptoapis-io/mcp-address-history)
- Supports EVM and UTXO address history
- Required env: CRYPTOAPIS_API_KEY
What problem does it solve?
On-chain history APIs are tedious to wrap per chain, so agents cannot quickly answer address-level questions during product integration.
Who is it for?
Builders adding wallet views, treasury tracking, or compliance research who already use or can obtain Crypto APIs keys.
Skip if: Non-crypto products, teams needing private mempool or trading execution, or users who cannot accept third-party indexed data.
What do I get? / Deliverables
Once CRYPTOAPIS_API_KEY is set, your agent can query full address transaction and token history through a single MCP tool surface.
- Agent-callable address history for EVM and UTXO via MCP
- Crypto APIs-backed transaction and token history queries
- stdio npm MCP server at version 0.3.0
Recommended MCP Servers
Journey fit
Blockchain data plumbing is Build work when you integrate wallets, explorers, or compliance views into your product. Address history calls are backend integrations against Crypto APIs, not launch marketing or production monitoring dashboards.
How it compares
Blockchain address-history API MCP, not a DeFi trading or smart-contract deploy skill.
Common Questions / FAQ
Who is CryptoAPIs MCP Address History for?
It is for developers building crypto-adjacent features who want MCP access to EVM and UTXO address transaction and token histories through Crypto APIs.
When should I use CryptoAPIs MCP Address History?
Use it while integrating on-chain read paths, debugging wallet activity, or validating address flows during Build-phase backend work.
How do I add CryptoAPIs MCP Address History to my agent?
Add @cryptoapis-io/mcp-address-history as a stdio MCP server in your client, set CRYPTOAPIS_API_KEY, and restart the agent session.