DataSinking vs Crypto Market Data MCP

A side-by-side look at the DataSinking and Crypto Market Data MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

DataSinking logoDataSinkingFinance & Fintech · Local subprocess (stdio)Full-text Asian financial reports (China, Korea, Japan) as clean Markdown — 6 tools for RAG agents.67GreatAuth: api key requiredCrypto Market Data MCP logoCrypto Market Data MCPFinance & Fintech · Local subprocess (stdio)Live crypto market data — price, funding rates, open interest, long/short ratio, order book, candles — across Bybit, Binance, OKX, Hyperliquid, Gate, KuCoin via CCXT, with funding-rate arbitrage comparison.59GoodAuth: api key required

Verdict: choose DataSinking for finance & fintech work as a local process; choose Crypto Market Data MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

DataSinking logoChoose DataSinking when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: DATASINK_API_KEY.
  • You want tools like list_exchanges, list_stocks, list_reports.
Explore DataSinking

Crypto Market Data MCP logoChoose Crypto Market Data MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You want tools like list_exchanges, get_capabilities, search_symbols.
Explore Crypto Market Data MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDataSinking logoDataSinkingCrypto Market Data MCP logoCrypto Market Data MCP
CategoryFinance & FintechFinance & Fintech
Quality signal67/100 · Great59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingNot declaredFree
Required env varsDATASINK_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars212
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools613

Tools & capabilities

DataSinking tools 6

  • list_exchangesList the exchanges DataSinking covers. Returns exchange codes (nyse / nasdaq / cboe / sse / szse / bj / jpx / ksc / koe / knx / twse / tpex / lse) with the number of reports available per exchange. Call this first to discover coverage. Sources: US = SEC EDGAR, A-shares = cninfo.com.cn, Japan = EDINET, Korea = DART, Taiwan = MOPS, UK = FCA NSM.
  • list_stocksList the stocks on one exchange, including the report count per company.
  • list_reportsList a company's reports — metadata only (id, title, period), no body text. Each item carries a `source` field naming the official disclosure platform; keep that attribution when you cite it.
  • get_reportFetch one report's full text (metadata + Markdown body). The `source` field names the official disclosure platform; keep that attribution when you cite it. Expensive in tokens — prefer get_section when you only need one chapter. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.
  • list_sectionsList every section of a report with its size, before you decide what to pull. Returns `sections` (titles, in order) plus `section_details` — same order, one entry per section with `title`, `has_tables`, `chars` and `estimated_tokens`. Use `estimated_tokens` to avoid pulling a chapter that would blow your context, and `has_tables` to know whether the chapter needs special handling (tables are the part RAG pipelines usually get wrong). Then call get_section with a heading keyword — the headings are in the report's own language.
  • get_sectionFetch only one section of a report by keyword — much cheaper than get_report, best for RAG. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.

Crypto Market Data MCP tools 13

  • list_exchangesWhich exchanges are supported
  • get_capabilitiesMatrix of which exchange supports which data (no network)
  • search_symbolsFind the exact symbol format for a coin
  • get_priceLast price + 24h stats
  • get_order_bookTop-of-book bids/asks
  • get_ohlcvRecent OHLCV candles
  • get_recent_tradesLatest public trades
  • get_funding_rateCurrent perpetual funding rate
  • get_funding_rate_historyHistorical funding rates
  • compare_fundingFunding rate across many exchanges + **arb spread
  • get_open_interestCurrent open interest
  • get_long_short_ratioGlobal long/short account ratio (Binance)
  • +1 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

DataSinking

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "datasinking": {
      "command": "npx",
      "args": [
        "-y",
        "datasinking-mcp"
      ],
      "env": {
        "DATASINK_API_KEY": "YOUR_DATASINK_API_KEY_HERE"
      }
    }
  }
}

Crypto Market Data MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "eliasfire617-crypto-market-data-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcpize"
      ]
    }
  }
}

Frequently asked questions

DataSinking is categorized under Finance & Fintech and uses a local stdio subprocess. Crypto Market Data MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick DataSinking for finance & fintech work and Crypto Market Data MCP for finance & fintech.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

DataSinking has no declared pricing — check the project's own site. Auth: api key required. Crypto Market Data MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add datasinking and eliasfire617-crypto-market-data-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, DataSinking has a quality signal of 67/100 (Great) with 1 views, 0 installs and 21 GitHub stars. Crypto Market Data MCP has 59/100 (Good) with 5 views, 0 installs and 2 GitHub stars.