Token OHLCV History API MCP Server

by br0ski777 Your server? Claim it

not responding

Token OHLCV History API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

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

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

130 ms

Response time

average over 24h

Stars

last commit 2 Sep 2026

What changed 3652

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

17 Sep a tool description was rewritten71 times that day token_get_ohlcv_history

16 Sep a tool description was rewritten92 times that day token_get_ohlcv_history

15 Sep a tool description was rewritten91 times that day token_get_ohlcv_history

14 Sep a tool description was rewritten91 times that day token_get_ohlcv_history

13 Sep a tool description was rewritten92 times that day token_get_ohlcv_history

12 Sep a tool description was rewritten91 times that day token_get_ohlcv_history

11 Sep a tool description was rewritten90 times that day token_get_ohlcv_history

10 Sep a tool description was rewritten93 times that day token_get_ohlcv_history

9 Sep a tool description was rewritten91 times that day token_get_ohlcv_history

8 Sep a tool description was rewritten91 times that day token_get_ohlcv_history

and 3642 more, back to 8 August 2026

Token OHLCV History API does not always answer

Over the last week it answered 30.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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

URL	Transport	State	Latency	Checked
https://token-ohlcv.api.klymax402.com/mcp	sse	answering	130 ms	11 min ago

Alternatives to Token OHLCV History API

same job, measured the same way

Tctc MCP

by kofujimura

ERC-7303 token-controlled roles for AI agents: grant, check, and revoke permissions on-chain

198 installs/wk local only

Capabilities

by eckari

Deterministic company, entity and location lookups for agents - per call, x402 or API key.

24 tools answering

x402-market

by asaishota

Let AI agents pay-per-call for any HTTP API via x402 on Base mainnet. One tool: pay_and_call.

36 installs/wk local only

MCP Address History

by cryptoapis-io

MCP server for full transaction and token history on EVM and UTXO addresses via Crypto APIs

44 installs/wk local only

Geckoterminal MCP

by mrfentmen

Token data from GeckoTerminal. No key required.

local only

Atlaspi

by soil911

Historical geography for AI agents: polities, GeoJSON borders, chains & events, 4500 BCE-today

160 installs/wk local only

Coingecko MCP Server

by cyanheads

Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata.

43 installs/wk local only

UniRate API

by unirate-api

Currency conversion and exchange rates for AI. 170+ currencies, historical data back to 1999.

27 installs/wk local only

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 0 of 91 checks got a reply (0.0%), average response time 130 ms. The bar chart above shows every period we have measured.

The registry lists Token OHLCV History API as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

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.

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.