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 (4 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 →
prepare_transactions__prepare_transactions_utxo ~323
Build unsigned UTXO transactions ready for signing (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). Returns the unsigned transaction and fee details. After preparing, sign locally (utxo_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native coin transfer, supporting multiple recipients in one transaction. Requires either feePriority or exactFee. Credits by action (source: OpenAPI): • native-coins: 530 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 |
| additionalData | string | – | OP_RETURN data to embed in the transaction |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| exactFee | string | – | Exact fee override in the chain's main denomination - required unless feePriority is given |
| feePriority | string | – | Fee priority tier - required unless exactFee is given |
| fromAddress | string | – | Sender's address (required) |
| locktime | integer | – | Transaction locktime |
| network | string | yes | Network name |
| prepareStrategy | string | – | UTXO selection strategy |
| recipients | array | – | Recipients as {address, amount} objects, amount in the chain's main denomination - one output per entry (required) |
| replaceable | boolean | – | Mark the transaction as RBF-replaceable |
No output schema declared.
No examples provided.
prepare_transactions__prepare_transactions_xrp ~230
Build unsigned XRP transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (xrp_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native XRP transfer 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 |
| amount | string | – | Amount in drops (required) |
| context | string | – | Optional context for the request - echoed back in response |
| destinationTag | string | – | Destination tag - commonly required when sending to an exchange address |
| feePriority | string | – | Fee priority tier - defaults to standard if omitted |
| fromAddress | string | – | Sender's XRP address (required) |
| network | string | yes | Network name |
| sequence | string | – | Override the account sequence number (advanced use) |
| toAddress | string | – | Recipient's XRP address (required) |
No output schema declared.
No examples provided.
prepare_transactions__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.
simulate__simulate_evm ~255
Dry-run an Ethereum transaction without broadcasting it to the network (mainnet or sepolia only — this endpoint does not support other EVM chains). Returns estimated gas usage, execution success/failure, and any revert reason. Use this to validate transactions before signing and broadcasting — helpful for catching errors, estimating costs, and debugging contract interactions. Credits per call: 48 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 |
| data | string | – | Hex-encoded calldata for contract interaction or deployment bytecode |
| fromAddress | string | yes | Sender address |
| gasLimit | string | – | Custom gas limit override (auto-estimated if omitted) |
| gasPrice | string | – | Custom gas price in wei (auto-estimated if omitted) |
| network | string | yes | Network name (Ethereum only — mainnet or sepolia) |
| toAddress | string | – | Recipient or contract address (omit for contract deployment simulation) |
| value | string | – | Amount in native coin's smallest unit, e.g. wei (defaults to '0') |
No output schema declared.
No examples provided.
simulate__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.
transactions_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.
transactions_data__transactions_data_evm ~338
Transactions Data EVM: get transaction details, internal transactions, token transfers, or logs by transaction hash. Actions: get-transaction-details, list-internal-transactions, list-token-transfers, list-logs. Credits by action (source: OpenAPI): • get-transaction-details: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • 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-logs: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 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 |
| network | string | yes | Network name |
| transactionHash | string | yes | Transaction hash |
No output schema declared.
No examples provided.
transactions_data__transactions_data_kaspa ~100
Transactions Data Kaspa: get transaction details by transaction ID. Network: mainnet. Credits per call: 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 |
|---|---|---|---|
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| transactionId | string | yes | Transaction ID |
No output schema declared.
No examples provided.
transactions_data__transactions_data_solana ~106
Transactions Data Solana: get transaction details by transaction hash (signature). Networks: mainnet, devnet. Credits per call: 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 |
|---|---|---|---|
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| transactionHash | string | yes | Transaction hash (signature) |
No output schema declared.
No examples provided.
transactions_data__transactions_data_utxo ~233
Transactions Data UTXO: get transaction details or raw transaction data by hash. Actions: get-transaction-details, get-raw-transaction-data. Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash. Networks: mainnet, testnet. Credits by action (source: OpenAPI): • get-raw-transaction-data: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • get-transaction-details: 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 |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| transactionHash | string | yes | Transaction hash |
No output schema declared.
No examples provided.
transactions_data__transactions_data_xrp ~101
Transactions Data XRP: get transaction details by transaction hash. Networks: mainnet, testnet. Credits per call: 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 |
|---|---|---|---|
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| transactionHash | string | yes | Transaction hash |
No output schema declared.
No examples provided.
utils__derive_addresses ~309
Utils: derive HD wallet (xPub, yPub, zPub) change or receiving addresses without syncing. GET /utils/{blockchain}/{network}/xpubs/{extendedPublicKey}/derive-addresses Derives up to 10 addresses. By default creates receiving/deposit address; set isChange=true for change address (UTXO only). Credits by action (source: OpenAPI): • binance-smart-chain: 25 • bitcoin: 10 • bitcoin-cash: 12 • dash: 11 • dogecoin: 11 • ethereum: 10 • ethereum-classic: 13 • litecoin: 11 • tron: 15 • xrp: 10 • zcash: 13 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 |
|---|---|---|---|
| addressFormat | string | – | Address format |
| addressesCount | integer | – | Number of addresses to derive (up to 10) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| extendedPublicKey | string | yes | xPub/yPub/zPub for the HD wallet |
| isChange | boolean | – | If true derive change address(es); if false derive receiving/deposit |
| network | string | yes | Network name |
| startIndex | integer | – | Starting index for derivation |
No output schema declared.
No examples provided.
utils__evm_utils ~265
EVM utils (Utils product): validate address, decode raw transaction hex. Actions: • validate-address: Check if an EVM address is valid • decode-raw-transaction: Decode a raw transaction hex Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • tron: mainnet, nile Credits by action (source: OpenAPI): • decode-raw-transaction: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15 • validate-address: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15 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 | – | Address (required for validate-address) |
| blockchain | string | yes | Blockchain protocol |
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| rawTransactionHex | string | – | Raw transaction hex (required for decode-raw-transaction) |
No output schema declared.
No examples provided.
utils__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.
utils__utxo_utils ~369
UTXO utils (Utils product): validate address, decode raw transaction hex, convert Bitcoin Cash address. Actions: • validate-address: Check if a UTXO address is valid • decode-raw-transaction: Decode a raw transaction hex • convert-bitcoin-cash-address: Convert Bitcoin Cash address (legacy ↔ cash format); Bitcoin Cash only, no blockchain parameter (network + address) 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): • convert-bitcoin-cash-address: bitcoin-cash 12 • decode-raw-transaction: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13 • validate-address: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13 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 | – | Address (required for validate-address and convert-bitcoin-cash-address) |
| blockchain | string | – | Blockchain protocol (required for validate-address and decode-raw-transaction) |
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name |
| rawTransactionHex | string | – | Raw transaction hex (required for decode-raw-transaction) |
No output schema declared.
No examples provided.
utils__xrp_utils ~241
XRP utils (Utils product): validate address, decode/encode X-Address. Actions: • validate-address: Check if an XRP address is valid • decode-x-address: Decode X-Address to classic address and tag • encode-x-address: Encode classic address and tag to X-Address Networks: mainnet, testnet Credits by action (source: OpenAPI): • decode-x-address: 10 • encode-x-address: 10 • validate-address: 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 |
| address | string | – | Address (required for validate-address) |
| addressTag | integer | – | Destination tag (required for encode-x-address) |
| classicAddress | string | – | Classic address (required for encode-x-address) |
| context | string | – | Optional context for the request - echoed back in response |
| network | string | yes | Network name: mainnet or testnet |
| xAddress | string | – | X-Address (required for decode-x-address) |
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.