Is Crypto APIs MCP Servers open source?

Unknown. Sato Hub has not found a public repository or a license statement for Crypto APIs MCP Servers as of 2026-10-15.

Which chains does Crypto APIs MCP Servers support?

Crypto APIs MCP Servers lists support for Multichain as of 2026-10-15.

Is Crypto APIs MCP Servers still maintained?

The most recent code activity Sato Hub observed was on 2026-03-13 (last commit 2026-03-13, last release 2026-03-13), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.

How do I install or run Crypto APIs MCP Servers?

remote. Install: connect to https://ai.cryptoapis.io/mcp with header x-api-key: YOUR_KEY (multi-tenant, no self-hosting needed) && or self-host one domain: npx @cryptoapis-io/mcp-address-latest --api-key YOUR_API_KEY && or install all domains: npm install @cryptoapis-io/mcp. Entry: {"mcpServers": {"cryptoapis": {"url": "https://ai.cryptoapis.io/mcp", "headers": {"x-api-key": "YOUR_API_KEY"}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://ai.cryptoapis.io/mcp).

MCP

Crypto APIs MCP Servers

Name: Crypto APIs MCP Servers
Author: Crypto APIs

Official Crypto APIs MCP suite: hosted endpoint plus per-package servers for balances, blocks, txs, fees, and market data.

Sato Score73
ChainsMultichain

UnknownSelf-ReportedQuiet · 7mo ago

Crypto APIs MCP Servers is a MCP server by Crypto APIs, with last code activity on 2026-03-13 (Quiet). Latest release on 2026-03-13. Sato Score 73/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Crypto APIs MCP Servers →

Last commit Mar 13, 2026 · Last release Mar 13, 2026

Listed from cryptoapis.io on 2026-07-13. Install: not attempted. Evidence →

Website ↗Docs ↗GitHub ↗

Next step

Watch Crypto APIs MCP Servers

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp

Run Sato Hub Preflight on cryptoapis-io/cryptoapis-mcp-hub before I use it.

Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Crypto APIs publishes an MCP hub with a hosted Streamable HTTP endpoint and package-level MCP servers covering wallet balances, blocks, transactions, fee estimates, events, contracts, and market data across the chains Crypto APIs supports. An agent builder plugs it in to give an agent multi-chain blockchain-data reads through one provider instead of wiring separate chain APIs. Usage runs through a Crypto APIs account and API key.

Sato Score

73/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness: 35/35
Code transparency: 8/20
Interface verifiability: 10/10
Docs & demo: 6/10
Listing transparency & provenance: 12/15
Independent verification: 2/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from cryptoapis.io on 2026-07-13. Install: not attempted.

Claim	Value	Evidence	Source	Checked
Chains supported	Multichain	self-reported	github.com/CryptoAPIs-io/cryptoapis-mcp-hub	as of 2026-10-15
Verification status	Self-Reported — not independently reviewed	self-reported	cryptoapis.io	as of 2026-10-15
Recent activity	last release 2026-03-13 · last commit 2026-03-13	observed	github.com/CryptoAPIs-io/cryptoapis-mcp-hub	2026-10-15
Install works	documented by the project, not run by Sato Hubnot attempted by Sato Hub	self-reported	github.com/CryptoAPIs-io/cryptoapis-mcp-hub	as of 2026-07-14
MCP endpoint answers	answered — 60 tools listed	observed	ai.cryptoapis.io	2026-10-15
Daily check record	43 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history	observed	—	2026-10-14
Deploys as	npm/npx, Docker, Hosted API (multi-tenant HTTP)confidence 0.90	self-reported	github.com/CryptoAPIs-io/cryptoapis-mcp-hub	as of 2026-07-14
Works with	Claude Desktop, Claude Code, Cursor, Windsurf, n8nconfidence 0.90	self-reported	github.com/CryptoAPIs-io/cryptoapis-mcp-hub	as of 2026-07-14
Sato Score	73/100 (High)how open, active and verifiable — not a safety or quality grade	computed	satohub.ai	2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: remote

connect to https://ai.cryptoapis.io/mcp with header x-api-key: YOUR_KEY (multi-tenant, no self-hosting needed)
or self-host one domain: npx @cryptoapis-io/mcp-address-latest --api-key YOUR_API_KEY
or install all domains: npm install @cryptoapis-io/mcp
{"mcpServers": {"cryptoapis": {"url": "https://ai.cryptoapis.io/mcp", "headers": {"x-api-key": "YOUR_API_KEY"}}}}

You supply: Crypto APIs API key (app.cryptoapis.io/api-keys), passed via the x-api-key header

Add to Cursor Add to VS Code

claude mcp add --transport http satohub-cryptoapis-mcp https://ai.cryptoapis.io/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-14. What a deploy spec is →

Tool inventory — 60 tools, probed live 2026-10-15

address_history__manage_address — 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 a
address_history__evm_address_history — Query EVM address full history (requires synced address). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-statistics: ethereum, eth
address_history__utxo_address_history — Query UTXO address full history (requires synced address). Pagination: • list-transactions, list-transactions-by-timestamp: cursor pagination (use 'nextStartingAfter' → 'startingAfter') • list-unspen
address_history__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
address_latest__evm_address_latest — Query latest EVM address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-balance: ethereum, ethereum-classic,
address_latest__utxo_address_latest — Query latest UTXO address data (last 14 days). • get-balance: no pagination • list-transactions: cursor pagination - use 'nextStartingAfter' from response as 'startingAfter' • list-unconfirmed-transac
address_latest__solana_address_latest — 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_latest__xrp_address_latest — 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 t
address_latest__kaspa_address_latest — Query latest Kaspa address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address KAS balance • list-transactions: Get address transact
address_latest__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
aml__aml — 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,
aml__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
block_data__evm_block_data — 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-bloc
block_data__utxo_block_data — 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-blo
block_data__xrp_block_data — 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-
block_data__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
blockchain_events__blockchain_events_manage — 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 a
blockchain_events__blockchain_events_create — 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
blockchain_events__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
blockchain_fees__blockchain_fees_utxo — 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. Action
blockchain_fees__blockchain_fees_evm — 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
blockchain_fees__blockchain_fees_xrp — 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 a
blockchain_fees__blockchain_fees_tezos — 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-tra
blockchain_fees__blockchain_fees_solana — 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 curren
blockchain_fees__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
broadcast__broadcast_signed_transaction — 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-si
broadcast__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
contracts__evm_contract_data — 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
contracts__solana_contract_data — 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: O
contracts__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
hd_wallet__manage_hd_wallet — 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
hd_wallet__hd_wallet_data_utxo — 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
hd_wallet__hd_wallet_data_evm — 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: •
hd_wallet__hd_wallet_data_xrp — 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: • de
hd_wallet__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
market_data__market_data_metadata — 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): • lis
market_data__market_data_exchange_rates — 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 t
market_data__market_data_assets — 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) Cr
market_data__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
prepare_transactions__prepare_transactions_evm — 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 bro
prepare_transactions__prepare_transactions_tezos — 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
prepare_transactions__prepare_transactions_solana — 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
prepare_transactions__prepare_transactions_kaspa — 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. Actio
prepare_transactions__prepare_transactions_xrp — 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:
prepare_transactions__prepare_transactions_utxo — 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)
prepare_transactions__prepare_transactions_tron — 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 ar
prepare_transactions__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
simulate__simulate_evm — 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/failu
simulate__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
transactions_data__transactions_data_utxo — 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, da
transactions_data__transactions_data_evm — 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
transactions_data__transactions_data_solana — 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
transactions_data__transactions_data_xrp — 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
transactions_data__transactions_data_kaspa — 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
transactions_data__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete
utils__utxo_utils — 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
utils__evm_utils — 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 Blockcha
utils__xrp_utils — 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 • e
utils__derive_addresses — 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 d
utils__system_info — CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete

Answers a handshake: yes · 2026-10-15
Answers a call: not asked — no tool is named as a read (list_/get_/search_)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

97.8%of 45 checks since 2026-09-01 succeeded

Currently responding for 1 day

Succeeded: 89
Failed: 2
Their error: 0
Unattributed: 2

State changed on 2026-08-04 (responding → unclear), 2026-08-05 (unclear → responding), 2026-10-14 (responding → unreachable from our probe), 2026-10-15 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded

100%

7-day rolling; unattributable days are gaps · 30/30 days

Tools listed

from the server's own tools/list · 29/30 days

Sato Score

as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Tool inventory history — 60 now, peak 60, since 2026-07-17

2026-09-23 0 → 60 +60 (address_history__evm_address_history, address_history__manage_address, address_history__system_info, address_history__utxo_address_history…)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.

Skills that target this — 1, with disclosures

Crypto APIsClawHub · oomol

400 installs

Crypto APIs (cryptoapis.io). Use this skill for ANY Crypto APIs request — searching and reading data. Whenever a task involves Crypto APIs, use this skill instead of calling the API directly.

Pipes a remote script into a shellGrants itself unrestricted tools

Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →

Details

Chains: Multichain
Agent types: MCP Server, Data Provider
Open source: Unknown
Pricing: Requires a Crypto APIs account; API usage billed per Crypto APIs plans
Deploys as: npm/npx, Docker, Hosted API (multi-tenant HTTP)
Works with: Claude Desktop, Claude Code, Cursor, Windsurf, n8n
Last checked: 2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#blockchain-data#market-data#api#multichain

Where Crypto APIs MCP Servers fits

Wallets Data

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Crypto APIs MCP Servers's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

Oct 15, 2026
Sato Score tier: Medium → High
Score 44 → 73.
Oct 14, 2026
Sato Score tier: High → Medium
Score 74 → 44.
Sep 23, 2026
Sato Score tier: Medium → High
Score 63 → 73.
Aug 5, 2026
Sato Score tier: Low → Medium
Score 39 → 61.
Aug 4, 2026
Sato Score tier: Medium → Low
Score 61 → 39.
Jul 18, 2026
Sato Hub began tracking this listing
Jul 14, 2026
Edited: mcp endpoint url
Jul 14, 2026
Auto-enriched: deployment options, supported integrations
Jul 14, 2026
Listed on Sato Hub

Compared with

Alternatives to Crypto APIs MCP Servers →

Appears in

Related Resources

Coinbase AgentKit

Active

Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain

Recent★ 1.3k

Hyperliquid

Active

VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid

Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active

Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown

Active★ 9.4k

Reference

QuestionsWhat people ask about this pageShowHide

Cite this pagePlain text, APA or BibTeXShowHide

Cite this page

Sato Hub. "Crypto APIs MCP Servers — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/cryptoapis-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Crypto APIs MCP Servers

Next step

Watch Crypto APIs MCP Servers

Check it from your agent

Your project?

Overview

Sato Score

Evidence — listed vs checked · what the words mean

Install — as documented by the project, not run by us

Tool inventory — 60 tools, probed live 2026-10-15

Observed record — 91 daily checks since 2026-07-17

Last 30 days — to 2026-10-15, one point per UTC day

Tool inventory history — 60 now, peak 60, since 2026-07-17

Skills that target this — 1, with disclosures

Crypto APIsClawHub · oomol

Details

Marketplace Signals

Where Crypto APIs MCP Servers fits

Listing History

Compared with

Appears in

Related Resources

Coinbase AgentKit

Hyperliquid

Model Context Protocol (MCP)

Questions people ask about Crypto APIs MCP Servers

Cite this page

Join the Sato Hub Briefing