DataRail

Agent-safe crypto financial data access layer.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Get Token Price: REQUIRED: token_id. Get current token price with validation and definitions.
  • Get Historical Price: REQUIRED: token_id, date. Get token price at a specific historical date — POINT-IN-TIME GUARANTEED. Unlike raw APIs that might return restated/survivorship-biased data, DataRail
  • Get Historical Chart: REQUIRED: token_id. Get historical price chart data (OHLCV-style) for a date range. Returns price, market cap, and volume arrays for analysis. Point-in-time guaranteed — data ref

What data it sees

Do you need an account

No: the server works without sign-in

Agent-safe crypto financial data access layer. Provides validated prices, market data, TVL, APY, survivorship bias checks, and cross-source validation (CoinGecko, CoinMarketCap, DeFiLlama). Every response includes source definitions, caveats, and data quality warnings.

How to connect

How to connect DataRail to Claude

The server address to paste into Claude settings:

https://data-rail--milesnee-e.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect DataRail to ChatGPT

The server address to paste into ChatGPT settings:

https://data-rail--milesnee-e.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect DataRail to Cursor

The server address to paste into Cursor settings:

https://data-rail--milesnee-e.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (14)

Raw names from tools/list. Only developers need these.

get_token_priceREQUIRED: token_id. Get current token price with validation and definitions.
get_historical_priceREQUIRED: token_id, date. Get token price at a specific historical date — POINT-IN-TIME GUARANTEED. Unlike raw APIs that might return restated/survivorship-biased data, DataRail validates that the price returned was actually observable at the requested date and checks for survivorship bias.
get_historical_chartREQUIRED: token_id. Get historical price chart data (OHLCV-style) for a date range. Returns price, market cap, and volume arrays for analysis. Point-in-time guaranteed — data reflects actual observed values at each timestamp during the period.
check_token_survivorshipREQUIRED: token_id. Check if a token is alive, dead, or delisted on CoinGecko. This is CRITICAL for backtesting: tokens that went to zero or were delisted won't appear in current market data, creating survivorship bias. DataRail tracks known dead tokens and can flag them in historical queries.
mark_token_dead_REQUIRED: token_id. Manually mark a token as dead in DataRail's survivorship registry. Use this when you've confirmed a token is dead/delisted/rug-pulled. DataRail will then flag this token in all future historical queries to prevent survivorship bias.
list_dead_tokens_List all tokens in DataRail's dead token registry. No parameters required. These tokens are known to be delisted, rug-pulled, or zero-value. They are flagged by survivorship-bias checks in historical queries.
get_token_market_dataREQUIRED: token_id. Get comprehensive market data for a token: price, market cap, volume, FDV, supply. Includes definitions and caveats for each field. CRITICAL: market_cap and volume_24h definitions differ between CoinGecko and CoinMarketCap — DataRail will warn you.
get_protocol_tvlREQUIRED: protocol_id. Get Total Value Locked for a DeFi protocol. Uses DeFiLlama (primary source). Includes definition of what 'TVL' means and what it does NOT include (staking, leverage, etc.).
get_protocol_poolsREQUIRED: protocol_id. Get pool/yield data for a DeFi protocol — TVL, APY, volume per pool. CRITICAL: APY values are BACKWARD-LOOKING 7-day annualized rates. They do NOT guarantee future returns and do NOT deduct impermanent loss. DataRail will always include this warning.
compare_field_definitionsREQUIRED: field. Compare how different data sources define the same financial field. Use this BEFORE comparing data across sources to avoid silent errors from definition mismatches.
check_data_compatibilityREQUIRED: field, source_a, source_b. Check if a field is safe to compare across two data sources. Returns a safety assessment with specific guidance.
validate_installValidate DataRail installation — check sources, config, and connectivity. No parameters required. Use this to verify DataRail is correctly configured before relying on it in Claude Desktop or Cursor. Tests CoinGecko + DeFiLlama connectivity and field definitions.
cross_validate_fieldREQUIRED: token_id. Cross-validate a field between CoinGecko and CoinMarketCap. Fetches the same field from both sources and compares them. Surfaces discrepancies with source-specific definitions so agents don't silently consume mismatched data. CRITICAL: market_cap and volume_24h WILL differ between CG and CMC because they use different circulating supply definitions. This tool makes the discrepancy EXPLICIT.
get_cmc_quoteREQUIRED: token_id. Get CoinMarketCap quote for a token. Useful as an alternative data source when cross-validating. CMC has DIFFERENT definitions for market_cap and volume vs CoinGecko.