MCP.so
ログイン

Token Ohlcv X402 MCP Server

@Br0ski777

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

Br0ski777

投稿者

Br0ski777

Token Ohlcv X402 MCP Server について

Historical OHLCV candles for any token -- daily, 4h, 1h intervals. CoinGecko + GeckoTerminal powered. -- x402 micropayment API + MCP server for AI agents

Token Ohlcv X402 MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "token-ohlcv": {
      "url": "https://token-ohlcv-production-0cce.up.railway.app/mcp",
      "transport": "sse"
    }
  }
}

Token Ohlcv X402 MCP Server のツール

1

GET

概要

What is Token Ohlcv X402?

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.

How to use Token Ohlcv X402?

Add the MCP server URL https://token-ohlcv.api.klymax402.com/mcp to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.). Use the token_get_ohlcv_history tool with parameters such as token ID, contract address, chain, days, and interval. Any x402-aware client handles the payment challenge automatically.

Key features of Token Ohlcv X402

  • Pay-per-call via x402 (USDC on Base L2)
  • No API key or signup required
  • 10,000+ tokens supported by CoinGecko ID or contract
  • Daily, 4-hour, and 1-hour candle intervals
  • Data sourced from CoinGecko and GeckoTerminal

Use cases of Token Ohlcv X402

  • Technical analysis and charting for any token
  • Backtesting trading strategies with historical OHLCV data
  • Trend detection and market analysis for AI agents
  • On-chain token price history lookup by contract address

よくある質問

1

What data sources does Token Ohlcv X402 use?

CoinGecko for token IDs and GeckoTerminal for on-chain contract lookups.

2

How does payment work?

It uses the x402 protocol — HTTP-native pay-per-call with USDC on Base L2, facilitated by Coinbase CDP (primary) and PayAI (fallback). No signup or API key is needed.

3

What intervals and historical ranges are available?

Daily (default), 4h (up to 90 days), and 1h (up to 2 days). Maximum 365 days total.

4

What is the cost per call?

Each call to `token_get_ohlcv_history` costs $0.002 USD.

5

What transports or authentication are supported?

MCP (SSE-based) via URL configuration. Also direct HTTP with x402 payment headers, and OAuth-wrapped via ATXP.

コメント

「その他」の他のコンテンツ