mcpbeat

Token OHLCV History API MCP Server

io.github.Br0ski777/token-ohlcv
answering

Token OHLCV History API is answering right now. Last checked 3 min ago. It exposes 1 tools. Last commit 19 Jul 2026.

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

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
38 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add token-ohlcv --transport http https://token-ohlcv.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "token-ohlcv": {
      "url": "https://token-ohlcv.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.token-ohlcv]
url = "https://token-ohlcv.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "token-ohlcv": {
      "url": "https://token-ohlcv.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "token-ohlcv": {
      "url": "https://token-ohlcv.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

token
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. 1. candles: array of candlestick objects with timestamp, open, high, low, close, volume 2. token: token identifier used 3. interval: candle interval (daily, 4h, 1h) 4. days: number of days of history returned 5. source: data source (CoinGecko or GeckoTerminal) Example output: {"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"} Use this FOR technical analysis, backtesting, trend detection, and charting. Supports 10,000+ tokens by CoinGecko ID or on-chain contract address via GeckoTerminal. Do NOT use for real-time orderbook -- use dex_analyze_orderbook_depth instead. Do NOT use for swap quotes -- use dex_get_swap_quote instead. Do NOT use for news -- use crypto_get_latest_news instead. Do NOT use for funding rates -- use perp_scan_funding_arbitrage instead.

Endpoints

URLTransportStateLatencyChecked
https://token-ohlcv.api.klymax402.com/mcp sse answering 15 ms 3 min ago

Token OHLCV History API — questions

Answers built from our own checks of this server.

What can Token OHLCV History API do?
It exposes 1 tools, read directly from the server on our last check. Among them: token_get_ohlcv_history. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Token OHLCV History API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 38 ms. The bar chart above shows every period we have measured.
How do I connect Token OHLCV History API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Token OHLCV History API need an API key?
No. Token OHLCV History API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Token OHLCV History API?
It answers our handshake in 38 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Token OHLCV History API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.