Tickdb Mcp — Real Time Market Data For Ai

Created By
TickDBan hour ago
TickDB MCP provides AI assistants with unified real-time and historical market data across Forex/FX, US/HK/A-share stocks (NASDAQ, NYSE), crypto, indices, and precious metals (XAU/XAG). 13 tools cover real-time quotes, ticker, order book depth, recent trades, and OHLCV candlestick (K-line) data over 37,527+ symbols. Powered by the TickDB unified market data API.
Overview

TickDB MCP — Real-Time Market Data for AI

TickDB MCP is a Model Context Protocol server that gives AI assistants direct access to real-time and historical market data through a single unified API.

Coverage

  • Forex / FX — EURUSD, USDJPY, GBPUSD …
  • Precious Metals — XAUUSD, XAGUSD
  • Indices — SPX, NDX, VIX, DXY
  • US Stocks (NASDAQ / NYSE) — AAPL.US, TSLA.US, NVDA.US
  • HK Stocks — 700.HK, 9988.HK
  • A-Shares — 600519.SH, 000858.SZ
  • Crypto — BTCUSDT, ETHUSDT
  • 37,527+ symbols across 6 major markets

13 Tools

Real-time quotes & ticker, OHLCV candlestick (K-line), latest live K-line, order book depth, recent trades, available symbols, K-line intervals, stock info, intraday data, trading sessions, trade calendar, market metrics, and capital flow.

Quick Start

  1. Get a free API key at tickdb.ai
  2. Add the config below to your MCP client
  3. Replace YOUR_API_KEY with your TickDB key

json { "mcpServers": { "tickdb": { "type": "http", "url": "https://mcp.tickdb.ai/", "headers": { "X-TickDB-Key": "YOUR_API_KEY" } } } } ​

Supported clients: Claude Code · Claude Desktop · Cursor · Kiro · Codex · Zed · Cherry Studio

Links: Website · Docs · GitHub

The MCP server is fully open source (Python · 13 tools · Docker-ready · MIT).

Server Config

{
  "mcpServers": {
    "tickdb": {
      "type": "http",
      "url": "https://mcp.tickdb.ai/",
      "headers": {
        "X-TickDB-Key": "YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
an hour ago
Updated At
an hour ago
Author Name
TickDB
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago