English Français العربية

Token OHLCV History API

Official registry Other

Historical OHLCV candles for any token. CoinGecko + GeckoTerminal on-chain. x402.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (sse)
Claude Code 
claude mcp add --transport sse token-ohlcv-history-api 'https://token-ohlcv.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "token-ohlcv-history-api": {
            "type": "sse",
            "url": "https://token-ohlcv.api.klymax402.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Token OHLCV History API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Token OHLCV History API

Historical OHLCV candles for any token -- daily, 4h, 1h intervals. CoinGecko + GeckoTerminal powered. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "token-ohlcv": {
      "url": "https://token-ohlcv.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl "https://token-ohlcv.api.klymax402.com/api/candles"
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
token_get_ohlcv_historyGET/api/candles$0.005Get historical OHLCV candles for any token by ID or contract address
token_get_ohlcv_historyPOST/api/candles$0.005Get historical OHLCV candles for any token by ID or contract address (POST variant)
token_get_ohlcv_history

Use this when you need historical price candlestick data for any token. Returns OHLCV candles in JSON.

Parameters

NameTypeRequiredDescription
tokenstringnoCoinGecko token ID (e.g. bitcoin, ethereum, solana). Use this OR contract+chain.
contractstringnoOn-chain contract address (e.g. 0x...). Use with chain parameter for GeckoTerminal lookup.
chainstringnoBlockchain network for contract lookup: base, ethereum, solana, arbitrum, polygon, optimism, bsc.
daysnumbernoNumber of days of history (default 30, max 365). For 1h interval max 2 days, for 4h max 90 days.
intervalstringnoCandle interval: daily (default), 4h (if days <= 90), 1h (if days <= 2).

Returns

  • candles -- array of candlestick objects with timestamp, open, high, low, close, volume
  • token -- token identifier used
  • interval -- candle interval (daily, 4h, 1h)
  • days -- number of days of history returned
  • source -- data source (CoinGecko or GeckoTerminal)

Example response:

{"candles":[{"timestamp":1712966400,"open":3105.20,"high":3142.80,"low":3089.50,"close":3128.60,"volume":1250000000}],"token":"ethereum","interval":"daily","days":30,"source":"CoinGecko"}

When to use: technical analysis, backtesting, trend detection, and charting. Supports 10,000+ tokens by CoinGecko ID or on-chain contract address via GeckoTerminal.

Not for: swap quotes (use dex_get_swap_quote), news (use crypto_get_latest_news), funding rates (use perp_scan_funding_arbitrage).

token_get_ohlcv_history

Use this when you need historical price candlestick data for any token. Returns OHLCV candles in JSON. POST variant of token_get_ohlcv_history -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
tokenstringnoCoinGecko token ID (e.g. bitcoin, ethereum, solana). Use this OR contract+chain.
contractstringnoOn-chain contract address (e.g. 0x...). Use with chain parameter for GeckoTerminal lookup.
chainstringnoBlockchain network for contract lookup: base, ethereum, solana, arbitrum, polygon, optimism, bsc.
daysnumbernoNumber of days of history (default 30, max 365). For 1h interval max 2 days, for 4h max 90 days.
intervalstringnoCandle interval: daily (default), 4h (if days <= 90), 1h (if days <= 2).

Returns

  • candles -- array of candlestick objects with timestamp, open, high, low, close, volume
  • token -- token identifier used
  • interval -- candle interval (daily, 4h, 1h)
  • days -- number of days of history returned
  • source -- data source (CoinGecko or GeckoTerminal)

Example response:

{"candles":[{"timestamp":1712966400,"open":3105.20,"high":3142.80,"low":3089.50,"close":3128.60,"volume":1250000000}],"token":"ethereum","interval":"daily","days":30,"source":"CoinGecko"}

When to use: technical analysis, backtesting, trend detection, and charting. Supports 10,000+ tokens by CoinGecko ID or on-chain contract address via GeckoTerminal.

Not for: swap quotes (use dex_get_swap_quote), news (use crypto_get_latest_news), funding rates (use perp_scan_funding_arbitrage).

Example agent prompts

  • "Historical price candlestick data for any token"
  • "Historical price candlestick data for any token"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Frequently asked questions

What is Token OHLCV History API?

Historical OHLCV candles for any token. CoinGecko + GeckoTerminal on-chain. x402.

How do I install Token OHLCV History API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse token-ohlcv-history-api 'https://token-ohlcv.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Token OHLCV History API need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Token OHLCV History API open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Token OHLCV History API?

It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.