mcpField
C
CryptoStruct Market Data

CryptoStruct Market Data

VerifiedFeaturedLocal
cryptostruct.comData & Analytics0Updated 10w ago

About CryptoStruct Market Data

CryptoStruct Market Data is a hosted remote MCP server for traders, quants, and AI agents working with crypto and prediction-market data. It combines a catalog of about 500,000 instruments with market statistics, historical files, and data purchasing.

Key features

  1. 01Search about 500,000 instruments
  2. 02Query live and aggregated market statistics
  3. 03Inspect slippage and market-impact curves
  4. 04Access free samples and tick data
  5. 05Manage orders and downloads via OAuth

Use cases

  1. 01Find Kalshi and Polymarket contracts
  2. 02Analyze historical markets and event data
  3. 03Compare market depth and slippage
  4. 04Purchase and download tick-data files

MCP support

The remote MCP server exposes instrument search, market statistics, data purchasing, and account-management tools to clients. Catalog, statistics, and guest purchasing work without an API key; account features are available through OAuth.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

CryptoStruct MCP Server

First-party remote MCP server for cryptostruct.com — historical crypto and prediction-market data (tick-level daily files from 35 venues including Kalshi and Polymarket) plus live market statistics, built for traders, quants and AI agents.

This repository documents the hosted server. There is nothing to install or run from here — the server is operated by CryptoStruct.

No API key required — the catalog, market stats and the guest purchase flow work keyless. Signing in via OAuth (optional) links your CryptoStruct account for order history, purchased-file downloads and paying with your credits — always with your consent (see Buying data).

Quick start

Claude Code

claude mcp add --transport http cryptostruct https://cryptostruct.com/mcp
# or, to enable account sign-in via OAuth:
claude mcp add --transport http cryptostruct https://cryptostruct.com/mcp/auth

Cursor / generic JSON config

{
  "mcpServers": {
    "cryptostruct": {
      "url": "https://cryptostruct.com/mcp"
    }
  }
}

claude.ai — Settings → Connectors → Add custom connector → https://cryptostruct.com/mcp/auth

What you can do

  • Catalog & discovery: search ~500K instruments across 35 venues (spot, perpetuals, futures, options, prediction markets), day-level archive coverage back to 2021-02-08.
  • Prediction markets: Kalshi and Polymarket event contracts are first-class instruments — searchable in the catalog (class=prediction), with coverage, live snapshots and minute/daily aggregates like any crypto instrument. Contracts quote 0..1 (USD); turnover comes USD-normalized.
  • Market statistics: live snapshots and minute/hourly/daily aggregates — OHLC, VWAP, trades, turnover, spreads, top-of-book depth; slippage / market-impact curves.
  • Buying data: raw tick files — crypto and prediction-market instruments alike — cost €1 per instrument-day. Card payments: the server hands off a Stripe checkout URL — payment happens in the user's browser, the server never touches card details. Free full-day sample files are available without any purchase.
  • Credits & agent consent (OAuth sign-in): account credits are never spent by an agent without the user's consent. By default create_checkout answers approval_required with an approval page where the user confirms (pay with credits or by card) or discards the order; unapproved orders expire after 24 h with nothing charged. Users can opt into autonomous purchases within limits (per-order and rolling 24-hour caps) at https://cryptostruct.com/account/agents — then fully credit-covered orders complete immediately; anything above the caps comes back for approval. The agent may additionally pass its own max_credit_cents. preview_checkout tells the agent in advance which of the three outcomes to expect. These settings can only be changed on the website, never through an agent's token.
  • Account tools (OAuth sign-in): list orders, get download URLs for purchased files, check subscription, credit balance and agent-spending settings.

Tools

ToolDescriptionTier
get_data_dictionaryData dictionary & product reference (file format, units, pricing)free
search_instrumentsSearch the instrument catalogfree
list_venuesList covered venuesfree
get_instrumentInstrument detailsfree
get_coverageDay-level archive coverage for an instrumentfree
list_sample_filesFree full-day sample filesfree
get_price_quotePrice quote for a set of data filesfree
get_market_snapshotLive market snapshot (60 min + 24 h)free
get_daily_statsDaily aggregates (30d–180d free; 365d/max Premium)free
get_hourly_statsHourly aggregates (7d–90d free; 180d Premium)free
get_slippageSlippage / market-impact curve (1h free; 24h/7d Premium)free
get_top_instrumentsTop instruments by live 24 h turnoverfree
get_movers24 h movers (gainers & losers)free
get_minutes_rangeHistorical minute series for event studiespremium
create_checkoutStart a purchase — Stripe URL (card) or approval_required / born-paid (credits, per the user's consent settings)commerce
get_checkout_statusPoll a checkout by session_id (card) or order_id (signed-in; credit/approval orders)commerce
get_order_filesList a paid order's files with download URLscommerce
request_file_restoreRestore an archived (cold-storage) filecommerce
list_my_ordersMy orderssign-in
get_my_filesMy purchased filessign-in
get_my_subscriptionMy subscription, credit balance & agent-spending settingssign-in
preview_checkoutDry run of a purchase: owned/unavailable files, credit cover, and whether create_checkout will complete, ask for approval, or hand off to Stripesign-in

Tiers: free/commerce work keyless. sign-in requires a verified OAuth sign-in (any account). premium tools/parameters require CryptoStruct Premium (€20/month) — which also unlocks longer stats windows (daily 365d/max, hourly 180d, slippage 24h/7d), larger search limits, a data-quality block in get_market_snapshot, and a 5× call budget. Calls beyond your tier return static AUTH_REQUIRED / PREMIUM_REQUIRED errors with an upgrade URL — never a hard failure.

Rate limits

Weighted per-caller budget: 120 units/min keyless (per IP) or per signed-in user, 600 units/min for Premium. Cheap catalog reads cost 1 unit, upstream-heavy stats 3–5, checkout 10. On RATE_LIMITED errors, back off for the indicated number of seconds.

Conventions

  • All file sizes are compressed (zstd) bytes; market values are USD; sale prices are EUR.
  • Minute-granularity data is retained ~30 days upstream; hourly/daily aggregates reach back further.
  • Tick files are full-day JSON-lines captures (orderbook snapshots & updates, trades, liquidations, funding, mark/index incl. options greeks). Format reference: Market Data Protocol.

Related

Support

Questions or issues: https://cryptostruct.com/contact

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.