A crypto market data MCP server for SQL research and backtests

By Cruscy Data · 2026-10-30

A crypto market data MCP server gives a compatible AI client structured tools for researching market records. Instead of asking a model to invent a dataset description or a backtest result, the client can request the catalog, inspect a schema, run a bounded query and retrieve the report of an actual experiment.

Connect to the data service

Cruscy Data exposes its MCP endpoint at https://data-mcp.cruscy.com/mcp. Create an API key in your account with the appropriate MCP scope, then configure a client that supports authenticated remote MCP connections:

{
  "mcpServers": {
    "cruscy-data": {
      "url": "https://data-mcp.cruscy.com/mcp",
      "headers": {"Authorization": "Bearer YOUR_CRUSCY_API_KEY"}
    }
  }
}

Client configuration formats differ. Follow your client's remote-transport instructions, keep the key out of shared prompts, and use the exact endpoint from the public documentation.

Inspect before querying

A useful research sequence is catalog_streams, then get_schema, followed by get_quality for the intended date. Confirm the symbol, market, readable date coverage, timestamp convention and units. Only then ask sql_query for a small aggregation that answers a specific question.

For example: compare the recorded spot spread across a documented hour, or inspect changes in a futures trade-flow measure. Ask the client to return the stream names, date filters and query with its explanation so another researcher can reproduce the result.

Keep tool output and interpretation separate

A fluent explanation is not evidence that a query ran. Preserve the actual tool response and any missing-data notice. If the service rejects an unavailable date or a query that exceeds its allowance, the client should report that result rather than substitute made-up rows.

The service also provides tools for saving a strategy, starting a supported spot backtest and retrieving its status and report. Inspect the strategy contract before submitting code. Access to futures data does not turn that spot execution contract into a perpetual-futures simulator.

Computation stays beside the records

Our subscription provides controlled computation over the recorded data, not bulk export of the source files. MCP shares the account's permissions and quotas with the other interfaces. Start with the documented free spot hour and retain the resulting query and report as your first reproducible example.