DataSinking vs PreReason MCP

A side-by-side look at the DataSinking and PreReason 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 requiredPreReason MCP logoPreReason MCPFinance & Fintech · Local subprocess (stdio)Pre-reasoned Bitcoin and macro market briefings with trend signals, confidence scores, and regime classification. 17 briefings covering BTC, Fed balance sheet, M2, Treasury yields, and cross-asset correlations.67GreatAuth: api key required

Verdict: choose DataSinking for finance & fintech work as a local process; choose PreReason 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

PreReason MCP logoChoose PreReason 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 have the keys it needs: PREREASON_API_KEY.
  • You want tools like list_briefings, list_metrics, get_health.
Explore PreReason MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDataSinking logoDataSinkingPreReason MCP logoPreReason MCP
CategoryFinance & FintechFinance & Fintech
Quality signal67/100 · Great67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingNot declaredFreemium
Required env varsDATASINK_API_KEYPREREASON_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars228
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools65

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.

PreReason MCP tools 5

  • list_briefingsList all available pre-reasoned market briefings with tier requirements. Returns 18 LIVE briefings across Free (6), Basic (6), and Pro (6) tiers. Covers Bitcoin, macro, FX, commodities, and cross-asset financial data categories. No authentication required.
  • list_metricsList all available individual metrics (119 metrics across bitcoin, macro, and calculated categories). Includes Bitcoin price, hash rate, Fed balance sheet, M2 supply, Treasury 10Y yield, net liquidity, and cross-asset indices (SPY, QQQ, VXX, UUP) used as BTC correlation signals. Optionally filter by category or search term. No authentication required.
  • get_healthCheck API health status, version, and available endpoints. No authentication required.
  • get_contextGet a pre-reasoned market briefing with trend signals, confidence scores, regime classification, and causal narratives for the requested domain (Bitcoin, macro, cross-asset, FX). Includes crypto, macro financial data, and cross-asset correlations (indices, bonds, volatility as BTC relationship signals). Output is decision-ready — designed to be consumed directly by reasoning agents, not parsed for individual values. Briefings are tier-gated: Free (btc.quick-check, btc.context, macro.snapshot, cross.correlations, btc.pulse, btc.grid-stress), Basic (btc.momentum, macro.liquidity, btc.on-chain, cross.breadth, btc.miner-survival, btc.etf-flows), Pro (btc.full, btc.factors, cross.regime, fx.liquidity, btc.energy, btc.treasury). Requires API key authentication via Authorization header.
  • get_metricGet a single metric with pre-reasoned signal interpretation, trend analysis (7d/30d/90d), confidence score with factor breakdown, momentum, and percentile ranking. Available metrics: bitcoin-price, bitcoin-market-cap, bitcoin-volume-24h, bitcoin-change-24h, bitcoin-dominance, bitcoin-hash-rate, bitcoin-difficulty, bitcoin-tx-count, bitcoin-tx-volume, bitcoin-active-addresses, fed-balance, m2-supply, treasury-10y, rrp, eur-usd, cny-usd, yield-curve, tga, treasury-3mo, treasury-2y, treasury-5y, treasury-30y, breakeven-5y, breakeven-10y, t5yifr, mortgage-30y, t10y3m-spread, auction-bid-to-cover-10y, auction-bid-to-cover-30y, indirect-bidder-pct, dealer-takedown-pct, next-treasury-auction-days, fed-funds-rate, ecb-deposit-rate, boj-policy-rate, fed-ecb-spread, fed-boj-spread, carry-trade-returns-proxy, carry-trade-velocity-1d, mortgage-treasury-spread, iwm-spy-credit-spread, spy-vxx-correlation-30d, regime-stability-flag, jpy-usd, oil-brent, oil-wti, ovx, real-rate-10y, gld-gdx-ratio, copper-gold-ratio, slv-sil-ratio, gdxj-gdx-ratio, gold-silver-ratio, brent-wti-spread, etf-gld-1h-velocity, etf-cper-1h-velocity, etf-uso-1h-velocity, etf-uup-velocity-1h, crude-oil-stocks, natgas-storage, oil-inventory-zscore, natgas-storage-zscore, ecb-boj-spread, etf-gld-volume, etf-uso-volume, etf-uup-volume, etf-gld-volume-zscore-30d, etf-uso-volume-zscore-30d, etf-uup-volume-zscore-30d, net-liquidity, hash-ribbon, mvrv-proxy, etf-spy, etf-qqq, etf-iwm, etf-vxx, etf-uup, etf-gld, etf-gdx, etf-gdxj, etf-slv, etf-sil, etf-uso, etf-ung, etf-cper, etf-weat, etf-tlt, etf-ibit, etf-fxe, etf-fxy, usdt-market-cap, usdt-dominance, btc-price-200d-ma, btc-price-200d-distance, btc-etf-net-flow, btc-etf-cumulative-flow, btc-etf-aum, btc-etf-ibit-flow, btc-etf-fbtc-flow, btc-etf-gbtc-flow, btc-etf-other-flow, btc-etf-ibit-aum, btc-etf-fbtc-aum, btc-etf-bitb-aum, btc-etf-arkb-aum, btc-etf-btco-aum, btc-etf-ezbc-aum, btc-etf-brrr-aum, btc-etf-hodl-aum, btc-etf-btcw-aum, btc-etf-gbtc-aum, btc-etf-btc-aum, bitcoin-price-1h-change-pct, raw-hashprice-tick, on-chain-velocity-30d, bitcoin-volume-zscore-30d, btc-perp-oi-contracts, btc-perp-positioning-regime, btc-perp-funding-zscore-30d. Requires API key authentication. Returns analyzed context (signal, trend direction, momentum, 90d percentile), not raw values. Use when you need to understand what a metric means for decision-making, not just its number.

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"
      }
    }
  }
}

PreReason MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "prereason-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@prereason/mcp"
      ],
      "env": {
        "PREREASON_API_KEY": "YOUR_PREREASON_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

DataSinking is categorized under Finance & Fintech and uses a local stdio subprocess. PreReason MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick DataSinking for finance & fintech work and PreReason 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. PreReason MCP is listed as freemium — a free tier with paid plans. 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 prereason-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 22 GitHub stars. PreReason MCP has 67/100 (Great) with 4 views, 0 installs and 8 GitHub stars.