io.github.CryptoAPIs-io/mcp
REMOTE · AI.CRYPTOAPIS.IO · 2 COMPONENTS
Combined Crypto APIs MCP server — all 14 products in one process
Available components
Last scanned (3 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 18804 tokens (~313/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 60 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://ai.cryptoapis.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.cryptoapis.io | CN=YR1,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | RSA 2048 | SHA256-RSA | 55e41aac7dac74253254a49541f636acdef |
| SANs: ai.cryptoapis.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai.cryptoapis.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| cryptoapis.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.cryptoapis.io/mcp | Verified | 200 | |
| http (plaintext) | http://ai.cryptoapis.io/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
address_history__evm_address_history ~609
Query EVM address full history (requires synced address). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-statistics: ethereum, ethereum-classic • list-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, tron • list-transactions-by-timestamp: ethereum, ethereum-classic (requires timestamp) • list-token-transfers: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-internal-transactions: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-tokens: ethereum, polygon, tron, ethereum-classic, binance-smart-chain Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-statistics: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-internal-transactions: binance-smart-chain 825, ethereum 330, ethereum-classic 429, polygon 660, tron 495 • list-token-transfers: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-tokens: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-transactions: binance-smart-chain 325, ethereum 130, ethereum-classic 169, polygon 260, tron 195 • list-transactions-by-timestamp: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| address | string | yes | Address to query |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
| timestamp | integer | – | Unix timestamp (starting point) for list-transactions-by-timestamp action |
No output schema declared.
No examples provided.
address_history__manage_address ~512
Manage synced addresses for Address History APIs. Cursor pagination for 'list': use 'nextStartingAfter' as 'startingAfter'. Actions: • sync: Add new address to sync (requires 'address') • list: Get all synced addresses for blockchain/network • activate: Reactivate a paused address (requires 'address') • delete: Remove synced address (requires 'address') Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Note: 'sync', 'activate', 'delete' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate: 30 • delete: 30 • list: 30 • sync: 30 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: sync, list, activate, delete |
| address | string | – | Address (required for sync, activate, delete) |
| blockchain | string | yes | Blockchain protocol |
| confirmationToken | string | – | Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
address_history__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
address_history__utxo_address_history ~537
Query UTXO address full history (requires synced address). Pagination: • list-transactions, list-transactions-by-timestamp: cursor pagination (use 'nextStartingAfter' → 'startingAfter') • list-unspent-outputs: offset pagination (use 'offset', response has 'total') Actions & supported blockchains: • get-statistics: bitcoin, bitcoin-cash • list-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash • list-transactions-by-timestamp: bitcoin, bitcoin-cash (requires timestamp) • list-unspent-outputs: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash (uses offset pagination) Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-statistics: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-transactions: bitcoin 130, bitcoin-cash 169, dash 143, dogecoin 143, litecoin 143, zcash 169 • list-transactions-by-timestamp: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-unspent-outputs: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| address | string | yes | Address to query |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| offset | integer | – | Pagination offset |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
| timestamp | integer | – | Unix timestamp (starting point) for list-transactions-by-timestamp action |
No output schema declared.
No examples provided.
address_latest__evm_address_latest ~696
Query latest EVM address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-balance: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • get-next-nonce: ethereum, ethereum-classic, binance-smart-chain (mainnet, mordor, testnet, sepolia) • list-transactions: ethereum, ethereum-classic, binance-smart-chain, arbitrum, polygon, avalanche (C-Chain), base, optimism, tron • list-token-transfers: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • list-internal-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, avalanche (C-Chain), arbitrum, base, optimism, tron Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-balance: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-next-nonce: arbitrum 32, avalanche 36, base 24, binance-smart-chain 50, ethereum 20, ethereum-classic 26, optimism 28, polygon 40, tron 30 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 • list-transactions: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 Credits are indicative only and may change at any time. The actual credits spent for each API request are…
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| address | string | yes | Address to query |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
address_latest__kaspa_address_latest ~241
Query latest Kaspa address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address KAS balance • list-transactions: Get address transactions Networks: mainnet (only) Credits by action (source: OpenAPI): • get-balance: kaspa 918 • list-transactions: kaspa 918 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: get-balance, list-transactions |
| address | string | yes | Kaspa address to query |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name: mainnet (only mainnet available) |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
address_latest__solana_address_latest ~270
Query latest Solana address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address SOL balance • list-transactions: Get address transactions • list-tokens: Get SPL tokens held by address Networks: mainnet, devnet Credits by action (source: OpenAPI): • get-balance: solana 75 • list-tokens: solana 120 • list-transactions: solana 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: get-balance, list-transactions, list-tokens |
| address | string | yes | Solana address to query |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name: mainnet or devnet |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
address_latest__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
address_latest__utxo_address_latest ~493
Query latest UTXO address data (last 14 days). • get-balance: no pagination • list-transactions: cursor pagination - use 'nextStartingAfter' from response as 'startingAfter' • list-unconfirmed-transactions: offset pagination - use 'limit' and 'offset' (lists unconfirmed/mempool transactions) Actions & supported blockchains: • get-balance: bitcoin, bitcoin-cash, litecoin, dash, dogecoin, zcash • list-transactions: bitcoin, bitcoin-cash, dash, dogecoin, litecoin, zcash • list-unconfirmed-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-balance: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • list-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • list-unconfirmed-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: get-balance, list-transactions, list-unconfirmed-transactions |
| address | string | yes | Address to query |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| offset | integer | – | Pagination offset |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
address_latest__xrp_address_latest ~270
Query latest XRP (Ripple) address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address XRP balance • list-transactions: Get address transactions • get-next-sequence: Get next available sequence number for transactions Networks: mainnet, testnet Credits by action (source: OpenAPI): • get-balance: xrp 20 • get-next-sequence: xrp 20 • list-transactions: xrp 110 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: get-balance, list-transactions, get-next-sequence |
| address | string | yes | XRP address to query |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name: mainnet or testnet |
| sortingOrder | string | – | Sort order: ascending (oldest first) or descending (newest first) |
| startingAfter | string | – | Pagination cursor - use nextStartingAfter from previous response |
No output schema declared.
No examples provided.
aml__aml ~674
AML (Anti-Money Laundering) risk checks for addresses and transactions. Actions: • verify-address: Check if a blockchain address is flagged or associated with fraud, sanctions, ransomware, exploits, darknet markets, or other AML risk categories. Returns risk score, risk band, and the flagging sources. • screen-transaction: Screen a transaction against AML data. Returns whether the transaction is flagged, its risk score/band, and the flagged participant addresses with their roles, scores, severities and categories. • get-address-exposure: Get an address's exposure to risky entities/categories across the AML exposure graph. Params: blockchain, address. Costs 200,000 credits per request. • list-address-exposure-paths: List the paths connecting an address to risky entities in the AML exposure graph. Params: blockchain, address; optional rootAddress (only return routes originating from this flagged root address), limit (1-50, defaults to 10), startingAfter (pagination cursor). Costs 100,000 credits per page - pass the response's next cursor back as startingAfter to fetch subsequent pages. get-address-exposure and list-address-exposure-paths only support a subset of chains - see the blockchain parameter description. Note: the credit cost of these endpoints is significant — see credits below. Credits by action (source: OpenAPI): • get-address-exposure: 200000 • list-address-exposure-paths: 100000 • screen-transaction: 500000 • verify-address: 200000 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| address | string | – | Blockchain address - required for verify-address, get-address-exposure, and list-address-exposure-paths |
| blockchain | string | – | Blockchain protocol - required for screen-transaction, get-address-exposure and list-address-exposure-paths. screen-transaction accepts: ethereum, ethereum-classic, binance-smart-chain, bitcoin, bitc… |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of exposure paths to return per page (1-50, defaults to 10) - applies to list-address-exposure-paths only |
| rootAddress | string | – | Only return routes that originate from this flagged root address (one of the roots[].rootAddress values returned by get-address-exposure) - optional, applies to list-address-exposure-paths only |
| startingAfter | string | – | Pagination cursor - pass the nextStartingAfter value from the previous response to fetch the next page; applies to list-address-exposure-paths only |
| transactionHash | string | – | Transaction hash to screen against AML data - required for screen-transaction |
No output schema declared.
No examples provided.
aml__system_info ~173
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
block_data__evm_block_data ~690
Get EVM block details (Block Data product). Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-hash: List transactions in a block by block hash • list-transactions-by-block-height: List transactions in a block by block height • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-block-by-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-block-by-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-last-mined-block: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-latest-mined-blocks: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockHash | string | – | Block hash (required for get-block-by-hash, list-transactions-by-block-hash) |
| blockHeight | integer | – | Block height (required for get-block-by-height, list-transactions-by-block-height) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| count | integer | – | Number of blocks to return (for list-latest-mined-blocks) |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| offset | integer | – | Pagination offset |
No output schema declared.
No examples provided.
block_data__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
block_data__utxo_block_data ~578
Get UTXO block details (Block Data product). Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-block-by-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-block-by-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-last-mined-block: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-latest-mined-blocks: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockHash | string | – | Block hash (required for get-block-by-hash, list-transactions-by-block-hash) |
| blockHeight | integer | – | Block height (required for get-block-by-height, list-transactions-by-block-height) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| count | integer | – | Number of blocks to return (for list-latest-mined-blocks) |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name |
| offset | integer | – | Pagination offset |
No output schema declared.
No examples provided.
block_data__xrp_block_data ~370
Get XRP block details (Block Data product). Path uses network only (no blockchain). Networks: mainnet, testnet. Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Credits by action (source: OpenAPI): • get-block-by-hash: 20 • get-block-by-height: 20 • get-last-mined-block: 20 • list-latest-mined-blocks: 20 • list-transactions-by-block-hash: 20 • list-transactions-by-block-height: 20 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockHash | string | – | Block hash (required for get-block-by-hash, list-transactions-by-block-hash) |
| blockHeight | integer | – | Block height (required for get-block-by-height, list-transactions-by-block-height) |
| context | string | – | Optional context for the request - echoed back in response |
| count | integer | – | Number of blocks to return (for list-latest-mined-blocks) |
| limit | integer | – | Number of items to return (max 50) |
| network | string | yes | Network name: mainnet or testnet |
| offset | integer | – | Pagination offset |
No output schema declared.
No examples provided.
blockchain_events__blockchain_events_create ~621
Create a webhook subscription for on-chain events. When the specified event occurs, CryptoAPIs sends a POST request to your callbackUrl with the event data. Subscriptions persist until deleted. Event types (supported blockchains vary per type — an invalid blockchain for the chosen eventType is rejected before calling the API): • address-coins-transactions-unconfirmed: fires when an unconfirmed coin transaction touches the address • address-coins-transactions-confirmed: fires once a coin transaction confirms (optionally on an exact confirmation via receiveCallbackOn) • address-coins-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-tokens-transactions-confirmed: fires once a token transfer confirms • address-tokens-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-internal-transactions-confirmed: fires once a confirmed internal (contract-internal) transaction touches the address • address-internal-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • block-mined: fires on every new block (no address field) All event types except block-mined require an address. Note: 'create' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits per call: 30 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address to monitor (required for all event types except block-mined) |
| allowDuplicates | boolean | – | Whether to allow duplicate subscriptions for the same address/event. The API requires this field even though the spec marks it optional (verified live) — defaults to false. |
| blockchain | string | yes | Blockchain protocol (e.g. bitcoin, ethereum); supported chains vary per eventType |
| callbackSecretKey | string | – | Secret key for HMAC-signing webhook payloads (recommended for verifying authenticity) |
| callbackUrl | string | yes | Webhook callback URL |
| confirmationToken | string | – | Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… |
| confirmationsCount | integer | – | Number of confirmations to track, sending a callback on each one (required for the '-each-confirmation' event types) |
| context | string | – | Optional context for the request - echoed back in response |
| eventType | string | yes | Event type to subscribe to |
| network | string | yes | Network name (e.g. mainnet, testnet, sepolia); supported networks vary per eventType |
| receiveCallbackOn | integer | – | Exact confirmation number to receive the callback on (address-coins-transactions-confirmed, address-tokens-transactions-confirmed, address-internal-transactions-confirmed only) |
No output schema declared.
No examples provided.
blockchain_events__blockchain_events_manage ~357
Manage existing webhook subscriptions for on-chain events. Use this to view, delete, or re-activate event subscriptions created via blockchain_events_create. Actions: • list-subscriptions: List all active subscriptions for a blockchain/network (paginated) • get-subscription: Get details of a specific subscription by its referenceId • delete-subscription: Remove a subscription (stops webhook delivery) • activate-subscription: Re-activate a previously deactivated subscription Note: 'delete-subscription', 'activate-subscription' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate-subscription: 12 • delete-subscription: 12 • get-subscription: 12 • list-subscriptions: 12 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockchain | string | – | Blockchain (required for all actions) |
| confirmationToken | string | – | Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… |
| context | string | – | Optional context for the request - echoed back in response |
| limit | number | – | Max results per page (list-subscriptions only) |
| network | string | – | Network (required for all actions) |
| offset | number | – | Pagination offset (list-subscriptions only) |
| referenceId | string | – | Subscription reference ID (for get, delete, activate) |
No output schema declared.
No examples provided.
blockchain_events__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
blockchain_fees__blockchain_fees_evm ~664
Get fee recommendations and estimate gas costs for EVM blockchains. Use this before preparing or signing a transaction to determine appropriate gas parameters. Actions: • get-fee-recommendations: Get recommended gas price tiers (slow/standard/fast) • get-eip-1559-fee-recommendations: Get EIP-1559 fee parameters (baseFee, maxPriorityFee) for supported chains • estimate-native-coin-transfer-gas: Estimate gas for a native coin transfer (e.g. ETH, BNB) • estimate-token-transfer-gas: Estimate gas for an ERC-20/ERC-721 token transfer • estimate-contract-interaction-gas: Estimate gas for a smart contract call Credits by action (source: OpenAPI): • estimate-contract-interaction-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • estimate-native-coin-transfer-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • estimate-token-transfer-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • get-eip-1559-fee-recommendations: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-fee-recommendations: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Token amount to transfer (required for estimate-token-transfer-gas) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | – | Token contract address (required for estimate-token-transfer-gas and estimate-contract-interaction-gas) |
| contractType | string | – | Token standard: ERC-20 or ERC-721 (estimate-token-transfer-gas only; defaults to ERC-20) |
| data | string | – | Hex-encoded calldata (required for estimate-contract-interaction-gas) |
| fromAddress | string | – | Sender address (required for gas estimation actions) |
| network | string | yes | Network name |
| toAddress | string | – | Recipient address (required for native coin and token transfer gas estimation) |
| value | string | – | Amount in native coin's smallest unit, e.g. wei (required for estimate-native-coin-transfer-gas; optional for estimate-contract-interaction-gas) |
No output schema declared.
No examples provided.
blockchain_fees__blockchain_fees_solana ~471
Blockchain Fees Solana: fee recommendations and compute-unit estimation. Solana uses compute units (not gas), so this is a distinct cost model from EVM. Actions: • get-fee-recommendations: Get current priority fee recommendations from the mempool • estimate-native-coin-transfer-compute-units: Estimate compute units for a native SOL transfer • estimate-token-transfer-compute-units: Estimate compute units for an SPL token transfer • estimate-program-invocation-compute-units: Estimate compute units for an arbitrary program instruction call Credits by action (source: OpenAPI): • estimate-native-coin-transfer-compute-units: 120 • estimate-program-invocation-compute-units: 120 • estimate-token-transfer-compute-units: 120 • get-fee-recommendations: 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | – | Accounts referenced by the instruction, in the order the program expects them (estimate-program-invocation-compute-units only; may be empty) |
| action | string | yes | Action to perform |
| amount | string | – | Amount in lamports (native) or token base units (token) - required for estimate-native-coin-transfer-compute-units, estimate-token-transfer-compute-units |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | – | SPL token mint address - required for estimate-token-transfer-compute-units |
| instructionData | string | – | Base58/base64-encoded instruction data for the program call - required for estimate-program-invocation-compute-units |
| network | string | yes | Network name |
| programId | string | – | On-chain program address to invoke - required for estimate-program-invocation-compute-units |
| recipient | string | – | Recipient address - required for estimate-native-coin-transfer-compute-units, estimate-token-transfer-compute-units |
| sender | string | – | Sender address - required for all estimate actions |
| tokenStandard | string | – | SPL token program standard - required for estimate-token-transfer-compute-units |
No output schema declared.
No examples provided.
blockchain_fees__blockchain_fees_tezos ~392
Blockchain Fees Tezos: fee recommendations and fee estimation for XTZ, FA1.2, and FA2 transfers. Actions: • get-fee-recommendations: Get current minimal fee/cost rates from the mempool • estimate-transfer: Estimate the fee for a native XTZ transfer • estimate-fa12-transfer: Estimate the fee for an FA1.2 token transfer • estimate-fa2-transfer: Estimate the fee for an FA2 token transfer Credits by action (source: OpenAPI): • estimate-fa12-transfer: 52 • estimate-fa2-transfer: 52 • estimate-transfer: 52 • get-fee-recommendations: 52 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Amount in mutez (transfer) or token base units (fa12/fa2) as an integer string - required for all estimate actions |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | – | FA1.2/FA2 token contract address - required for estimate-fa12-transfer, estimate-fa2-transfer |
| network | string | yes | Network name |
| recipient | string | – | Recipient address - required for estimate-transfer, estimate-fa12-transfer, estimate-fa2-transfer |
| sender | string | – | Sender address - required for estimate-transfer, estimate-fa12-transfer, estimate-fa2-transfer |
| senderPublicKey | string | – | Sender's public key - required only when the source account is unrevealed (all estimate actions) |
| tokenId | string | – | FA2 token ID as an integer STRING (e.g. "0") - estimate-fa2-transfer only; the API rejects a number |
No output schema declared.
No examples provided.
blockchain_fees__blockchain_fees_utxo ~312
Get fee recommendations for UTXO blockchains (bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash). Use this before preparing or signing a transaction to determine the appropriate fee rate. Actions: • get-fee-recommendations: Get recommended fee-per-byte tiers (slow/standard/fast) from the mempool • estimate-transaction-smart-fee: Estimate the fee rate needed for confirmation within a target number of blocks Credits by action (source: OpenAPI): • estimate-transaction-smart-fee: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • get-fee-recommendations: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockchain | string | yes | Blockchain protocol |
| confirmationTarget | integer | – | Target number of blocks for confirmation (estimate-transaction-smart-fee only) |
| context | string | – | Optional context for the request - echoed back in response |
| feeRatePriority | string | – | Fee rate priority: ECONOMICAL or CONSERVATIVE (estimate-transaction-smart-fee only) |
| network | string | yes | Network name |
No output schema declared.
No examples provided.
blockchain_fees__blockchain_fees_xrp ~91
Blockchain Fees XRP: get fee recommendations. Networks: mainnet, testnet. Credits per call: 20 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
No output schema declared.
No examples provided.
blockchain_fees__system_info ~175
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
broadcast__broadcast_signed_transaction ~301
Broadcast locally signed transaction (Broadcast product). Submit a signed transaction hex to the network. Supported blockchains and networks vary; see credits for per-chain cost. Note: 'broadcast-signed-transaction' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • broadcast-signed-transaction: arbitrum 80, avalanche 90, base 60, binance-smart-chain 125, bitcoin 50, bitcoin-cash 60, dash 55, dogecoin 55, ethereum 50, ethereum-classic 65, litecoin 55, optimism 70, polygon 100, solana 150, tezos 65, tron 75, xrp 50, zcash 65 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| blockchain | string | yes | Blockchain protocol |
| confirmationToken | string | – | Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… |
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| signedTransactionHex | string | yes | Signed transaction hex to broadcast |
No output schema declared.
No examples provided.
broadcast__system_info ~173
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
contracts__evm_contract_data ~206
Get EVM contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details (name, symbol, standard, decimals, totalSupply) by contract address Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: binance-smart-chain 75, ethereum 30, ethereum-classic 39 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | yes | Contract address (token contract) |
| network | string | yes | Network name |
No output schema declared.
No examples provided.
contracts__solana_contract_data ~148
Get Solana contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details by contract address Networks: mainnet, devnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: 75 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | yes | Contract address (token contract) |
| network | string | yes | Network name: mainnet or devnet |
No output schema declared.
No examples provided.
contracts__system_info ~173
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
hd_wallet__hd_wallet_data_evm ~461
Query HD wallet data for EVM blockchains by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • prepare-transaction: Build an unsigned EVM transaction from a wallet address • list-assets: List token balances (ERC-20, ERC-721, etc.) held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 120 • prepare-transaction: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockchain | string | – | EVM blockchain (e.g. ethereum, binance-smart-chain, polygon); required for all actions |
| context | string | – | Optional context for the request - echoed back in response |
| data | string | – | Hex-encoded calldata for contract interaction (prepare-transaction only) |
| extendedPublicKey | string | – | xPub/yPub/zPub for this chain |
| feePriority | string | – | Fee priority level (prepare-transaction only; defaults to standard) |
| fromAddress | string | – | Sender address (required for prepare-transaction) |
| limit | number | – | Max results per page (for list-* actions) |
| network | string | – | Network (e.g. mainnet, sepolia); required for all actions |
| offset | number | – | Pagination offset (for list-* actions) |
| toAddress | string | – | Recipient address (required for prepare-transaction) |
| value | string | – | Amount in the native coin's smallest unit, e.g. wei (required for prepare-transaction) |
No output schema declared.
No examples provided.
hd_wallet__hd_wallet_data_utxo ~518
Query HD wallet data for UTXO blockchains (bitcoin, litecoin, bitcoin-cash, dogecoin, dash, zcash) by extended public key (xPub/yPub/zPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • derive-change-address: Derive the next unused change address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • list-utxos: List unspent transaction outputs (UTXOs) for the wallet • prepare-transaction: Build an unsigned UTXO transaction with automatic input selection • list-assets: List token/asset balances held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-change-address: 24 • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 120 • list-utxos: 120 • prepare-transaction: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| addressFormat | string | – | UTXO list-addresses: address format |
| blockchain | string | – | UTXO blockchain (e.g. bitcoin, litecoin, bitcoin-cash, dogecoin, dash, zcash); required for all actions |
| context | string | – | Optional context for the request - echoed back in response |
| derivation | string | – | UTXO list-utxos / list-transactions: derivation type |
| extendedPublicKey | string | – | xPub/yPub/zPub for this chain |
| feePriority | string | – | Fee priority level (prepare-transaction only; defaults to standard) |
| limit | number | – | Max results per page (for list-* actions) |
| network | string | – | Network (e.g. mainnet, testnet); required for all actions |
| offset | number | – | Pagination offset (for list-* actions) |
| recipients | array | – | Array of {address, amount} objects (required for prepare-transaction) |
No output schema declared.
No examples provided.
hd_wallet__hd_wallet_data_xrp ~344
Query HD wallet data for XRP (Ripple) by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • list-assets: List token/asset balances held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| addressFormat | string | – | XRP list-addresses: address format |
| context | string | – | Optional context for the request - echoed back in response |
| derivation | string | – | XRP list-transactions: derivation type |
| extendedPublicKey | string | – | xPub for XRP |
| isChangeAddress | boolean | – | XRP list-addresses: filter change addresses |
| limit | number | – | Max results per page (for list-* actions) |
| network | string | – | XRP network (mainnet or testnet); required for all actions |
| offset | number | – | Pagination offset (for list-* actions) |
No output schema declared.
No examples provided.
hd_wallet__manage_hd_wallet ~404
Manage HD wallets identified by extended public key (xPub/yPub/zPub). Private keys never leave the user's device — only the extended public key is sent to CryptoAPIs for address derivation and balance tracking. Actions: • sync-wallet: Register an xPub to start syncing its addresses and balances • list-wallets: List all synced HD wallets for a blockchain/network • activate-wallet: Re-activate a previously deleted wallet • delete-wallet: Remove an xPub from tracking (can be re-activated later) • get-status: Check the sync status of a wallet (syncing, synced, etc.) Note: 'sync-wallet', 'activate-wallet', 'delete-wallet' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate-wallet: 12 • delete-wallet: 12 • get-status: 10 • list-wallets: 12 • sync-wallet: 36 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| blockchain | string | – | Blockchain; required for all actions |
| confirmationToken | string | – | Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… |
| context | string | – | Optional context for the request - echoed back in response |
| extendedPublicKey | string | – | xPub/yPub/zPub; required for sync, activate, delete, get-status |
| limit | number | – | Max results per page (list-wallets only) |
| network | string | – | Network; required for all actions |
| offset | number | – | Pagination offset (list-wallets only) |
No output schema declared.
No examples provided.
hd_wallet__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
market_data__market_data_assets ~196
Market Data assets (asset details). Actions: • get-asset-details-by-asset-id: Get asset details by unique asset ID • get-asset-details-by-asset-symbol: Get asset details by symbol (e.g. BTC, ETH) Credits by action (source: OpenAPI): • get-asset-details-by-asset-id: 10 • get-asset-details-by-asset-symbol: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| assetId | string | – | Asset ID - for get-asset-details-by-asset-id |
| assetSymbol | string | – | Asset symbol (e.g. BTC) - for get-asset-details-by-asset-symbol |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
market_data__market_data_exchange_rates ~262
Market Data exchange rates. Actions: • get-exchange-rate-by-asset-symbols: Get exchange rate between two assets by symbol (e.g. BTC, USD) • get-exchange-rate-by-asset-ids: Get exchange rate between two assets by asset ID Credits by action (source: OpenAPI): • get-exchange-rate-by-asset-ids: 10 • get-exchange-rate-by-asset-symbols: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| context | string | – | Optional context for the request - echoed back in response |
| fromAssetId | string | – | From asset ID - for get-exchange-rate-by-asset-ids |
| fromAssetSymbol | string | – | From asset symbol (e.g. BTC) - for get-exchange-rate-by-asset-symbols |
| toAssetId | string | – | To asset ID - for get-exchange-rate-by-asset-ids |
| toAssetSymbol | string | – | To asset symbol (e.g. USD) - for get-exchange-rate-by-asset-symbols |
No output schema declared.
No examples provided.
market_data__market_data_metadata ~149
Market Data metadata (list supported assets). Actions: • list-supported-assets: List supported crypto and fiat assets (optional pagination and type filter) Credits by action (source: OpenAPI): • list-supported-assets: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| context | string | – | Optional context for the request - echoed back in response |
| limit | integer | – | Number of items to return (max 50) |
| offset | integer | – | Pagination offset |
| type | string | – | Asset type filter (crypto or fiat) |
No output schema declared.
No examples provided.
market_data__system_info ~174
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
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Reference topic to retrieve |
| context | string | – | Optional context for the request - echoed back in response |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_evm ~395
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Token amount to transfer (required for prepare-fungible-token-transfer) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | – | Token contract address (required for prepare-fungible-token-transfer and prepare-nft-transfer) |
| fromAddress | string | – | Sender address (required for all actions) |
| gasLimit | string | – | Custom gas limit override (prepare-transaction-from-address only; auto-estimated if omitted) |
| gasPrice | string | – | Custom gas price in wei (prepare-transaction-from-address only; auto-estimated if omitted) |
| network | string | yes | Network name |
| toAddress | string | – | Recipient address (required for all actions) |
| tokenId | string | – | NFT token ID (required for prepare-nft-transfer) |
| value | string | – | Amount in native coin's smallest unit, e.g. wei (required for prepare-transaction-from-address) |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_kaspa ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| context | string | – | Optional context for the request - echoed back in response |
| exactFee | string | – | Exact fee override in KAS - bypasses mass-based fee calculation when set |
| feePriority | string | – | Fee priority tier - defaults to standard if omitted |
| fromAddress | string | – | Sender's Kaspa address (required) |
| locktime | integer | – | Transaction locktime |
| network | string | yes | Network name - Kaspa is mainnet-only |
| prepareStrategy | string | – | UTXO selection strategy |
| recipients | array | – | Recipients as {address, amount} objects, amount in KAS main units - one output per entry, multiple recipients supported in a single transaction (required) |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_solana ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Amount in lamports for native-coins, or token base units for spl-tokens (required for all actions) |
| context | string | – | Optional context for the request - echoed back in response |
| feePriority | string | – | Fee priority tier - defaults to standard if omitted |
| fromAddress | string | – | Sender address (required for all actions) |
| network | string | yes | Network name |
| toAddress | string | – | Recipient address (required for all actions) |
| tokenContract | string | – | SPL token mint address (required for spl-tokens) |
| tokenStandard | string | – | SPL token program standard (spl-tokens only) |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_tezos ~366
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Amount to send, in mutez for native-coins, or in the token's base units for fa1-2-tokens/fa2-tokens (required for all actions) |
| context | string | – | Optional context for the request - echoed back in response |
| contractAddress | string | – | FA1.2/FA2 token contract address (KT1...) - required for fa1-2-tokens, fa2-tokens |
| feePriority | string | – | Fee priority tier - defaults to standard if omitted |
| fromAddress | string | – | Sender's Tezos address (required for all actions) |
| fromPublicKey | string | – | Sender's public key - required only when the source account is unrevealed |
| network | string | yes | Network name |
| toAddress | string | – | Recipient's Tezos address (required for all actions) |
| tokenId | string | – | FA2 token ID - required for fa2-tokens |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_tron ~365
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| amount | string | – | Amount in sun for native-coins, or token base units for trc20-tokens (required for native-coins, trc20-tokens) |
| context | string | – | Optional context for the request - echoed back in response |
| contract | string | – | Token contract address (required for trc20-tokens, non-fungible-tokens) |
| feeLimit | integer | – | Max TRX fee limit in sun (trc20-tokens, non-fungible-tokens only) |
| network | string | yes | Network name |
| recipient | string | – | Recipient's Tron address (required for all actions) |
| sender | string | – | Sender's Tron address (required for all actions) |
| tokenId | string | – | NFT token ID (required for non-fungible-tokens) |
No output schema declared.
No examples provided.
How do I install the io.github.CryptoAPIs-io/mcp server?
io.github.CryptoAPIs-io/mcp is a hosted endpoint at https://ai.cryptoapis.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai.cryptoapis.io
claude mcp add --transport http cryptoapis-io-mcp 'https://ai.cryptoapis.io/mcp'
What is the io.github.CryptoAPIs-io/mcp server?
io.github.CryptoAPIs-io/mcp is listed in the public MCP registry as io.github.CryptoAPIs-io/mcp. Combined Crypto APIs MCP server, all 14 products in one process. This page covers its hosted endpoint (https://ai.cryptoapis.io/mcp).
Is the io.github.CryptoAPIs-io/mcp server safe to use?
io.github.CryptoAPIs-io/mcp scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CryptoAPIs-io/mcp server expose?
io.github.CryptoAPIs-io/mcp exposes 60 tools: address_history__manage_address, address_history__evm_address_history, address_history__utxo_address_history, address_history__system_info, address_latest__evm_address_latest, and 55 more. Their descriptions and schemas cost roughly 18,804 tokens of context every time the server is loaded.
Does the io.github.CryptoAPIs-io/mcp server require authentication?
Yes. io.github.CryptoAPIs-io/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.CryptoAPIs-io/mcp server still maintained?
io.github.CryptoAPIs-io/mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.