SiteCheck Crypto & Finance
MCP server · api.chainmarket-api.workers.dev · found in a public list · checked since 2026-10-24
Live, handshake completed · latest check
https://api.chainmarket-api.workers.dev/mcp?ref=registry MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 124 endpoints from chainmarket-api.workers.dev.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
crypto_1inch_pathfinder_quotescrypto_aave_lending_marketscrypto_arbiscan_l2_rollupcrypto_balancer_v2_poolscrypto_basescan_contract_eventscrypto_berachain_pol_validatorscrypto_binance_orderbook_depthcrypto_bitcoin_hashrate_difficultycrypto_bitcoin_mempool_statscrypto_blast_gold_pointscrypto_chainlink_price_feedscrypto_circle_cctp_transferscrypto_coinbase_spot_exchangecrypto_coingecko_market_depthcrypto_coinmarketcap_listingscrypto_compound_market_statscrypto_convex_vlcvx_votingcrypto_cowswap_batch_auctionscrypto_cross_chain_bridge_flowscrypto_crypto_fundraising_roundscrypto_crypto_hack_rekt_databasecrypto_crypto_liquidations_feedcrypto_curve_gauge_weightscrypto_debank_wallet_portfoliocrypto_defillama_stablecoinscrypto_defillama_tvl_oraclecrypto_defillama_yieldscrypto_deribit_options_skewcrypto_dex_pool_liquiditycrypto_dydx_chain_marketscrypto_ethereum_gas_telemetrycrypto_ethereum_staking_rewardscrypto_etherscan_label_cloudcrypto_fear_greed_indexcrypto_gmx_v2_glv_vaultscrypto_honeypot_detectorcrypto_hyperliquid_perps_depthcrypto_jupiter_solana_routingcrypto_lido_steth_pegcrypto_linea_consensys_rollup+88
- Tools
- 128
- This list since
- 2026-10-24
- First listed to us
- 2026-10-24
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
crypto_smart_contract_verify address* chainIdcrypto_honeypot_detector address* chainIdcrypto_dex_pool_liquidity chain* pool*crypto_defillama_tvl_oracle protocol*crypto_defillama_stablecoins symbolscrypto_defillama_yields project chain symbolcrypto_whale_alert_transfers minBtc limitcrypto_token_holder_concentration address*crypto_aave_lending_markets symbolcrypto_compound_market_stats marketcrypto_nft_floor_wash_detector address*crypto_cross_chain_bridge_flows limit
From the tool list it returned to our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-25. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 137 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_363dca7714a65795