Data Collection
tickdb.ai
Provides real-time and historical cryptocurrency market data including ticker, kline, order book, and recent trades.
ENDPOINT 1
https://mcp.tickdb.ai
MCP server metadata
- Name
- tickdb-market-data
- Version
- 1.27.2
Real-time and historical market data for forex, precious metals, indices, US stocks, Hong Kong stocks, A-shares, and cryptocurrencies via TickDB API. Symbol formats: Crypto: BTCUSDT, ETHUSDT Forex: EURUSD, GBPUSD, USDJPY Metals: XAUUSD, XAGUSD Indices: SPX, DJI, IXIC, NDX, VIX, DXY US stocks: AAPL.US, TSLA.US, NVDA.US HK stocks: 700.HK, 9988.HK A-shares: 600519.SH, 000858.SZ A valid TickDB API key is required. Register at https://tickdb.ai to obtain one. Pass your key via the X-TickDB-Key request header or set TICKDB_API_KEY on the server.
Known tools 13
get_kline_latestGet the most recent (live/incomplete) K-line candle for one or more symbols.
Inferred read-onlyget_trade_daysGet the trading calendar (trading days and half-days) for a date range.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tickdb-market-data]
url = "https://mcp.tickdb.ai"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tickdb-market-data": {
"type": "http",
"url": "https://mcp.tickdb.ai"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tickdb-market-data
Remote MCP URL: https://mcp.tickdb.ai
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tickdb-market-data": {
"url": "https://mcp.tickdb.ai"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tickdb-market-data": {
"type": "http",
"url": "https://mcp.tickdb.ai"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tickdb-market-data",
"transport": "streamable-http",
"url": "https://mcp.tickdb.ai"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.