CryptoAPIs-io MCP server
io.github.CryptoAPIs-io/mcpCryptoAPIs-iostreamable-httpv0.6.0Scanned
Combined Crypto APIs MCP server — all 14 products in one process
60 tools: 4 can delete or cancel things, 6 do something that can't be undone, 36 change things and 14 only read.
- Reads private data · 0
- Reads text others write · 46
- Can send data out · 9
- 10 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things and 6 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CryptoAPIs-io MCP server can do
The CryptoAPIs-io MCP server is published by the GitHub account CryptoAPIs-io. It has 60 tools. It can delete or cancel things (4 tools: address_history__manage_address, blockchain_events__blockchain_events_manage, broadcast__broadcast_signed_transaction and hd_wallet__manage_hd_wallet), do things that cannot be undone, such as sending, paying or publishing (blockchain_fees__blockchain_fees_tezos, blockchain_fees__blockchain_fees_solana, broadcast__system_info, prepare_transactions__prepare_transactions_kaspa and 2 more) and create or change data (36 tools: address_history__system_info, address_latest__system_info, aml__aml, aml__system_info and 32 more). 14 tools only read.
46 tools bring in text other people can write (address_history__manage_address, address_history__evm_address_history, address_history__utxo_address_history and 43 more); 9 tools can send data out of your system (blockchain_events__blockchain_events_create, blockchain_fees__blockchain_fees_tezos, blockchain_fees__blockchain_fees_solana and 6 more).
The fixed checks matched 10 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 0.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
60 tools
Deletes or cancels 4Claude Code: deny
address_history__manage_addressManage synced addresses for Address History APIs.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
blockchain_events__blockchain_events_manageManage existing webhook subscriptions for on-chain events.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
broadcast__broadcast_signed_transactionBroadcast locally signed transaction (Broadcast product).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "broadcast__broadcast_signed_transaction" says "broadcast": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "broadcast__broadcast_signed_transaction" says "broadcast": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
hd_wallet__manage_hd_walletManage HD wallets identified by extended public key (xPub/yPub/zPub).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Can't be undone 6Claude Code: ask
blockchain_fees__blockchain_fees_solanaBlockchain Fees Solana: fee recommendations and compute-unit estimation.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipient): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Findings
- Warn
The server marks "blockchain_fees__blockchain_fees_solana" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blockchain_fees__blockchain_fees_tezosBlockchain Fees Tezos: fee recommendations and fee estimation for XTZ, FA1.2, and FA2 transfers.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipient): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Findings
- Warn
The server marks "blockchain_fees__blockchain_fees_tezos" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
broadcast__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.Can send data out1 finding
Why it is in this group
- The name "broadcast__system_info" says "broadcast": a word for sending, and what is sent cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "broadcast__system_info" says "broadcast": it sends or publishes something to other people.
Findings
- Warn
The server marks "broadcast__system_info" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "broadcast__system_info" says "broadcast": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
prepare_transactions__prepare_transactions_kaspaBuild unsigned Kaspa transactions ready for signing.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipients): what the tool writes goes there.
Findings
- Warn
The server marks "prepare_transactions__prepare_transactions_kaspa" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipients): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__prepare_transactions_tronBuild unsigned Tron transactions ready for signing.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipient): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Findings
- Warn
The server marks "prepare_transactions__prepare_transactions_tron" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__prepare_transactions_utxoBuild unsigned UTXO transactions ready for signing (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipients): what the tool writes goes there.
Findings
- Warn
The server marks "prepare_transactions__prepare_transactions_utxo" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipients): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 36Claude Code: ask
address_history__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
address_latest__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
aml__amlAML (Anti-Money Laundering) risk checks for addresses and transactions.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
aml__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
block_data__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
blockchain_events__blockchain_events_createCreate a webhook subscription for on-chain events.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "blockchain_events__blockchain_events_create" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callbackUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
blockchain_events__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
blockchain_fees__blockchain_fees_xrpBlockchain Fees XRP: get fee recommendations.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blockchain_fees__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
contracts__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
hd_wallet__hd_wallet_data_evmQuery HD wallet data for EVM blockchains by extended public key (xPub).Reads text others write1 finding
Why it is in this group
- The description's first verb is "query": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "hd_wallet__hd_wallet_data_evm" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
hd_wallet__hd_wallet_data_utxoQuery HD wallet data for UTXO blockchains (bitcoin, litecoin, bitcoin-cash, dogecoin, dash, zcash) by extended public key (xPub/yPub/zPub).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "query": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipients): what the tool writes goes there.
Findings
- Warn
The server marks "hd_wallet__hd_wallet_data_utxo" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
hd_wallet__hd_wallet_data_xrpQuery HD wallet data for XRP (Ripple) by extended public key (xPub).Reads text others write1 finding
Why it is in this group
- The description's first verb is "query": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "hd_wallet__hd_wallet_data_xrp" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
hd_wallet__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_data__market_data_assetsMarket Data assets (asset details).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
market_data__market_data_exchange_ratesMarket Data exchange rates.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
market_data__market_data_metadataMarket Data metadata (list supported assets).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
market_data__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
prepare_transactions__prepare_transactions_evmBuild unsigned EVM transactions ready for signing.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__prepare_transactions_solanaBuild unsigned Solana transactions ready for signing.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__prepare_transactions_tezosBuild unsigned Tezos operations ready for signing.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__prepare_transactions_xrpBuild unsigned XRP transactions ready for signing.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prepare_transactions__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
simulate__simulate_evmDry-run an Ethereum transaction without broadcasting it to the network (mainnet or sepolia only — this endpoint does not support other EVM chains).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
simulate__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
transactions_data__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
transactions_data__transactions_data_evmTransactions Data EVM: get transaction details, internal transactions, token transfers, or logs by transaction hash.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transactions_data__transactions_data_kaspaTransactions Data Kaspa: get transaction details by transaction ID.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transactions_data__transactions_data_solanaTransactions Data Solana: get transaction details by transaction hash (signature).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transactions_data__transactions_data_utxoTransactions Data UTXO: get transaction details or raw transaction data by hash.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transactions_data__transactions_data_xrpTransactions Data XRP: get transaction details by transaction hash.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
utils__derive_addressesUtils: derive HD wallet (xPub, yPub, zPub) change or receiving addresses without syncing.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
utils__evm_utilsEVM utils (Utils product): validate address, decode raw transaction hex.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
utils__system_infoCryptoAPIs reference documentation — no API call, no credits consumed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
utils__utxo_utilsUTXO utils (Utils product): validate address, decode raw transaction hex, convert Bitcoin Cash address.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
utils__xrp_utilsXRP utils (Utils product): validate address, decode/encode X-Address.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 14Show 14 read-only tools
address_history__evm_address_historyQuery EVM address full history (requires synced address).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_history__utxo_address_historyQuery UTXO address full history (requires synced address).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_latest__evm_address_latestQuery latest EVM address data (last 14 days).Reads text others write1 finding
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,033 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e actual credits spent for each API request are returned in the response headers."
Description, as the server wrote it 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 returned in the response headers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_latest__kaspa_address_latestQuery latest Kaspa address data.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_latest__solana_address_latestQuery latest Solana address data (last 14 days).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_latest__utxo_address_latestQuery latest UTXO address data (last 14 days).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_latest__xrp_address_latestQuery latest XRP (Ripple) address data.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "query": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
block_data__evm_block_dataGet EVM block details (Block Data product).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
block_data__utxo_block_dataGet UTXO block details (Block Data product).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
block_data__xrp_block_dataGet XRP block details (Block Data product).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blockchain_fees__blockchain_fees_evmGet fee recommendations and estimate gas costs for EVM blockchains.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
blockchain_fees__blockchain_fees_utxoGet fee recommendations for UTXO blockchains (bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
contracts__evm_contract_dataGet EVM contract token details (Contracts product).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
contracts__solana_contract_dataGet Solana contract token details (Contracts product).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write46
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- address_history__evm_address_history
- address_history__manage_address
- address_history__utxo_address_history
- address_latest__evm_address_latest
- address_latest__kaspa_address_latest
- address_latest__solana_address_latest
- address_latest__utxo_address_latest
- address_latest__xrp_address_latest
- aml__aml
- block_data__evm_block_data
- block_data__utxo_block_data
- block_data__xrp_block_data
- and 34 more
- Can send data out9
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
- blockchain_events__blockchain_events_create
- blockchain_fees__blockchain_fees_solana
- blockchain_fees__blockchain_fees_tezos
- broadcast__broadcast_signed_transaction
- broadcast__system_info
- hd_wallet__hd_wallet_data_utxo
- prepare_transactions__prepare_transactions_kaspa
- prepare_transactions__prepare_transactions_tron
- prepare_transactions__prepare_transactions_utxo
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 46
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 46 tools that change things (4 destructive, 6 irreversible, 36 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ai.cryptoapis.io/mcp: tools/list returned 60 tools to an anonymous client, including address_history__manage_address (destructive), blockchain_events__blockchain_events_manage (destructive), broadcast__broadcast_signed_transaction (destructive), hd_wallet__manage_hd_wallet (destructive), blockchain_fees__blockchain_fees_tezos (irreversible) and 41 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 43 to 46
Findings
Matches of fixed checks, with the text they matched.
The server marks "blockchain_fees__blockchain_fees_tezos" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
The server marks "blockchain_fees__blockchain_fees_solana" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
The server marks "broadcast__system_info" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "broadcast__system_info" says "broadcast": a word for sending, and what is sent cannot be taken back.
The server marks "hd_wallet__hd_wallet_data_utxo" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
The server marks "hd_wallet__hd_wallet_data_evm" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
The server marks "hd_wallet__hd_wallet_data_xrp" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "query": a word for reading.
Show 4 more findingsShow fewer
The server marks "prepare_transactions__prepare_transactions_kaspa" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipients): what it sends cannot be taken back.
The server marks "prepare_transactions__prepare_transactions_utxo" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipients): what it sends cannot be taken back.
The server marks "prepare_transactions__prepare_transactions_tron" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.recipient): what it sends cannot be taken back.
The description is 2,033 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e actual credits spent for each API request are returned in the response headers."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools60 changed.~60 changedView diff
- Changed:address_history__evm_address_historyOnly readstitleannotations
- Changed:address_history__manage_addressDeletes or cancelstitleannotations
- Changed:address_history__system_infoChanges thingstitleannotations
- Changed:address_history__utxo_address_historyOnly readstitleannotations
- Changed:address_latest__evm_address_latestOnly readstitleannotations
- Changed:address_latest__kaspa_address_latestOnly readstitleannotations
- Changed:address_latest__solana_address_latestOnly readstitleannotations
- Changed:address_latest__system_infoChanges thingstitleannotations
- Changed:address_latest__utxo_address_latestOnly readstitleannotations
- Changed:address_latest__xrp_address_latestOnly readstitleannotations
- Changed:aml__amlChanges thingstitleannotations
- Changed:aml__system_infoChanges thingstitleannotations
- Changed:block_data__evm_block_dataOnly readstitleannotations
- Changed:block_data__system_infoChanges thingstitleannotations
- Changed:block_data__utxo_block_dataOnly readstitleannotations
- Changed:block_data__xrp_block_dataOnly readstitleannotations
- Changed:blockchain_events__blockchain_events_createChanges thingstitleannotations
- Changed:blockchain_events__blockchain_events_manageDeletes or cancelstitleannotations
- Changed:blockchain_events__system_infoChanges thingstitleannotations
- Changed:blockchain_fees__blockchain_fees_evmOnly readstitleannotations
- Changed:blockchain_fees__blockchain_fees_solanaCan't be undonetitleannotations
- Changed:blockchain_fees__blockchain_fees_tezosCan't be undonetitleannotations
- Changed:blockchain_fees__blockchain_fees_utxoOnly readstitleannotations
- Changed:blockchain_fees__blockchain_fees_xrpChanges thingstitleannotations
- Changed:blockchain_fees__system_infoChanges thingstitleannotations
- Changed:broadcast__broadcast_signed_transactionDeletes or cancelstitleannotations
- Changed:broadcast__system_infoCan't be undonetitleannotations
- Changed:contracts__evm_contract_dataOnly readstitleannotations
- Changed:contracts__solana_contract_dataOnly readstitleannotations
- Changed:contracts__system_infoChanges thingstitleannotations
- Changed:hd_wallet__hd_wallet_data_evmChanges thingstitleannotations
- Changed:hd_wallet__hd_wallet_data_utxoChanges thingstitleannotations
- Changed:hd_wallet__hd_wallet_data_xrpChanges thingstitleannotations
- Changed:hd_wallet__manage_hd_walletDeletes or cancelstitleannotations
- Changed:hd_wallet__system_infoChanges thingstitleannotations
- Changed:market_data__market_data_assetsChanges thingstitleannotations
- Changed:market_data__market_data_exchange_ratesChanges thingstitleannotations
- Changed:market_data__market_data_metadataChanges thingstitleannotations
- Changed:market_data__system_infoChanges thingstitleannotations
- Changed:prepare_transactions__prepare_transactions_evmChanges thingstitleannotations
- Changed:prepare_transactions__prepare_transactions_kaspaCan't be undonetitleannotations
- Changed:prepare_transactions__prepare_transactions_solanaChanges thingstitleannotations
- Changed:prepare_transactions__prepare_transactions_tezosChanges thingstitleannotations
- Changed:prepare_transactions__prepare_transactions_tronCan't be undonetitleannotations
- Changed:prepare_transactions__prepare_transactions_utxoCan't be undonetitleannotations
- Changed:prepare_transactions__prepare_transactions_xrpChanges thingstitleannotations
- Changed:prepare_transactions__system_infoChanges thingstitleannotations
- Changed:simulate__simulate_evmChanges thingstitleannotations
- Changed:simulate__system_infoChanges thingstitleannotations
- Changed:transactions_data__system_infoChanges thingstitleannotations
- Changed:transactions_data__transactions_data_evmChanges thingstitleannotations
- Changed:transactions_data__transactions_data_kaspaChanges thingstitleannotations
- Changed:transactions_data__transactions_data_solanaChanges thingstitleannotations
- Changed:transactions_data__transactions_data_utxoChanges thingstitleannotations
- Changed:transactions_data__transactions_data_xrpChanges thingstitleannotations
- Changed:utils__derive_addressesChanges thingstitleannotations
- Changed:utils__evm_utilsChanges thingstitleannotations
- Changed:utils__system_infoChanges thingstitleannotations
- Changed:utils__utxo_utilsChanges thingstitleannotations
- Changed:utils__xrp_utilsChanges thingstitleannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 43 -> 46.View diff
- Tools that change things, listed without credentials: 43 to 46
Install
Pinned to version 0.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cryptoapis-io https://ai.cryptoapis.io/mcp --header 'x-api-key: <your-x-api-key>'claude mcp add --transport http cryptoapis-io https://ai.cryptoapis.io/mcp --header 'x-api-key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cryptoapis-io__address_history__evm_address_history",
"mcp__cryptoapis-io__address_history__utxo_address_history",
"mcp__cryptoapis-io__address_latest__evm_address_latest",
"mcp__cryptoapis-io__address_latest__utxo_address_latest",
"mcp__cryptoapis-io__address_latest__solana_address_latest",
"mcp__cryptoapis-io__address_latest__xrp_address_latest",
"mcp__cryptoapis-io__address_latest__kaspa_address_latest",
"mcp__cryptoapis-io__block_data__evm_block_data",
"mcp__cryptoapis-io__block_data__utxo_block_data",
"mcp__cryptoapis-io__block_data__xrp_block_data",
"mcp__cryptoapis-io__blockchain_fees__blockchain_fees_utxo",
"mcp__cryptoapis-io__blockchain_fees__blockchain_fees_evm",
"mcp__cryptoapis-io__contracts__evm_contract_data",
"mcp__cryptoapis-io__contracts__solana_contract_data"
],
"ask": [
"mcp__cryptoapis-io__address_history__system_info",
"mcp__cryptoapis-io__address_latest__system_info",
"mcp__cryptoapis-io__aml__aml",
"mcp__cryptoapis-io__aml__system_info",
"mcp__cryptoapis-io__block_data__system_info",
"mcp__cryptoapis-io__blockchain_events__blockchain_events_create",
"mcp__cryptoapis-io__blockchain_events__system_info",
"mcp__cryptoapis-io__blockchain_fees__blockchain_fees_xrp",
"mcp__cryptoapis-io__blockchain_fees__blockchain_fees_tezos",
"mcp__cryptoapis-io__blockchain_fees__blockchain_fees_solana",
"mcp__cryptoapis-io__blockchain_fees__system_info",
"mcp__cryptoapis-io__broadcast__system_info",
"mcp__cryptoapis-io__contracts__system_info",
"mcp__cryptoapis-io__hd_wallet__hd_wallet_data_utxo",
"mcp__cryptoapis-io__hd_wallet__hd_wallet_data_evm",
"mcp__cryptoapis-io__hd_wallet__hd_wallet_data_xrp",
"mcp__cryptoapis-io__hd_wallet__system_info",
"mcp__cryptoapis-io__market_data__market_data_metadata",
"mcp__cryptoapis-io__market_data__market_data_exchange_rates",
"mcp__cryptoapis-io__market_data__market_data_assets",
"mcp__cryptoapis-io__market_data__system_info",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_evm",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_tezos",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_solana",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_kaspa",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_xrp",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_utxo",
"mcp__cryptoapis-io__prepare_transactions__prepare_transactions_tron",
"mcp__cryptoapis-io__prepare_transactions__system_info",
"mcp__cryptoapis-io__simulate__simulate_evm",
"mcp__cryptoapis-io__simulate__system_info",
"mcp__cryptoapis-io__transactions_data__transactions_data_utxo",
"mcp__cryptoapis-io__transactions_data__transactions_data_evm",
"mcp__cryptoapis-io__transactions_data__transactions_data_solana",
"mcp__cryptoapis-io__transactions_data__transactions_data_xrp",
"mcp__cryptoapis-io__transactions_data__transactions_data_kaspa",
"mcp__cryptoapis-io__transactions_data__system_info",
"mcp__cryptoapis-io__utils__utxo_utils",
"mcp__cryptoapis-io__utils__evm_utils",
"mcp__cryptoapis-io__utils__xrp_utils",
"mcp__cryptoapis-io__utils__derive_addresses",
"mcp__cryptoapis-io__utils__system_info"
],
"deny": [
"mcp__cryptoapis-io__address_history__manage_address",
"mcp__cryptoapis-io__blockchain_events__blockchain_events_manage",
"mcp__cryptoapis-io__broadcast__broadcast_signed_transaction",
"mcp__cryptoapis-io__hd_wallet__manage_hd_wallet"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cryptoapis-io. Review it before you use it.
Capability tags behind 47 rules
- mcp__cryptoapis-io__address_history__manage_address untrusted-input
- mcp__cryptoapis-io__address_history__evm_address_history untrusted-input
- mcp__cryptoapis-io__address_history__utxo_address_history untrusted-input
- mcp__cryptoapis-io__address_latest__evm_address_latest untrusted-input
- mcp__cryptoapis-io__address_latest__utxo_address_latest untrusted-input
- mcp__cryptoapis-io__address_latest__solana_address_latest untrusted-input
- mcp__cryptoapis-io__address_latest__xrp_address_latest untrusted-input
- mcp__cryptoapis-io__address_latest__kaspa_address_latest untrusted-input
- mcp__cryptoapis-io__aml__aml untrusted-input
- mcp__cryptoapis-io__block_data__evm_block_data untrusted-input
- mcp__cryptoapis-io__block_data__utxo_block_data untrusted-input
- mcp__cryptoapis-io__block_data__xrp_block_data untrusted-input
- mcp__cryptoapis-io__blockchain_events__blockchain_events_manage untrusted-input
- mcp__cryptoapis-io__blockchain_events__blockchain_events_create untrusted-input, outbound
- mcp__cryptoapis-io__blockchain_fees__blockchain_fees_utxo untrusted-input
- mcp__cryptoapis-io__blockchain_fees__blockchain_fees_evm untrusted-input
- mcp__cryptoapis-io__blockchain_fees__blockchain_fees_xrp untrusted-input
- mcp__cryptoapis-io__blockchain_fees__blockchain_fees_tezos untrusted-input, outbound
- mcp__cryptoapis-io__blockchain_fees__blockchain_fees_solana untrusted-input, outbound
- mcp__cryptoapis-io__broadcast__broadcast_signed_transaction untrusted-input, outbound
- mcp__cryptoapis-io__broadcast__system_info outbound
- mcp__cryptoapis-io__contracts__evm_contract_data untrusted-input
- mcp__cryptoapis-io__contracts__solana_contract_data untrusted-input
- mcp__cryptoapis-io__hd_wallet__manage_hd_wallet untrusted-input
- mcp__cryptoapis-io__hd_wallet__hd_wallet_data_utxo untrusted-input, outbound
- mcp__cryptoapis-io__hd_wallet__hd_wallet_data_evm untrusted-input
- mcp__cryptoapis-io__hd_wallet__hd_wallet_data_xrp untrusted-input
- mcp__cryptoapis-io__market_data__market_data_metadata untrusted-input
- mcp__cryptoapis-io__market_data__market_data_exchange_rates untrusted-input
- mcp__cryptoapis-io__market_data__market_data_assets untrusted-input
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_evm untrusted-input
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_tezos untrusted-input
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_solana untrusted-input
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_kaspa untrusted-input, outbound
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_xrp untrusted-input
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_utxo untrusted-input, outbound
- mcp__cryptoapis-io__prepare_transactions__prepare_transactions_tron untrusted-input, outbound
- mcp__cryptoapis-io__simulate__simulate_evm untrusted-input
- mcp__cryptoapis-io__transactions_data__transactions_data_utxo untrusted-input
- mcp__cryptoapis-io__transactions_data__transactions_data_evm untrusted-input
- mcp__cryptoapis-io__transactions_data__transactions_data_solana untrusted-input
- mcp__cryptoapis-io__transactions_data__transactions_data_xrp untrusted-input
- mcp__cryptoapis-io__transactions_data__transactions_data_kaspa untrusted-input
- mcp__cryptoapis-io__utils__utxo_utils untrusted-input
- mcp__cryptoapis-io__utils__evm_utils untrusted-input
- mcp__cryptoapis-io__utils__xrp_utils untrusted-input
- mcp__cryptoapis-io__utils__derive_addresses untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.CryptoAPIs-io/mcp/verify?hash=67c7d439916832171b66fdc0a7add543e0e156be2d2bd8d5e7e794171d681d6a" | jq -e '.changed == false'Pinned hash 67c7d4399168, from Nov 13, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.CryptoAPIs-io/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.CryptoAPIs-io/mcp)Source: MCP Registry · repository. Synced Nov 13, 2026, 12:17 UTC.
CryptoAPIs-io MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CryptoAPIs-io MCP server safe?
- No scan can promise that. What its definitions show: 60 tools, 46 of which can change, send or delete something, and 10 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CryptoAPIs-io MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: address_history__manage_address, blockchain_events__blockchain_events_manage, broadcast__broadcast_signed_transaction and hd_wallet__manage_hd_wallet.
Can the CryptoAPIs-io MCP server do things that cannot be undone?
- Yes. 6 tools can send, pay, publish or merge: blockchain_fees__blockchain_fees_tezos, blockchain_fees__blockchain_fees_solana, broadcast__system_info, prepare_transactions__prepare_transactions_kaspa, prepare_transactions__prepare_transactions_utxo and prepare_transactions__prepare_transactions_tron.
What tools does the CryptoAPIs-io MCP server have?
- 60 tools: 4 destructive, 6 irreversible, 36 write, 14 read. address_history__manage_address, blockchain_events__blockchain_events_manage, broadcast__broadcast_signed_transaction, hd_wallet__manage_hd_wallet, blockchain_fees__blockchain_fees_tezos, blockchain_fees__blockchain_fees_solana, broadcast__system_info, prepare_transactions__prepare_transactions_kaspa and 52 more.
Does the CryptoAPIs-io MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CryptoAPIs-io MCP server send data to outside services?
- 9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): blockchain_events__blockchain_events_create, blockchain_fees__blockchain_fees_tezos, blockchain_fees__blockchain_fees_solana, broadcast__broadcast_signed_transaction, broadcast__system_info, hd_wallet__hd_wallet_data_utxo and 3 more.
Has the CryptoAPIs-io MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.