tilla-mcp
OfficialA read-only MCP server for TILLA market data — crypto, US stocks/ETFs, FX, macro and node data on one UTC clock — with 14 tools for discovery, retrieval, live ticks, corrections and plan info.
Explore without a key: what TILLA is, feed status, plans and limits, newest bar of every lane (health), and the full API manual in one call.
Browse markets: list every market with category, related markets and lanes, then pull one whole market (e.g.
btc,nvda,eurusd,gold) in a single call, optionally including related markets and paged byseries_next_offset.Inspect your access: see exactly which series your key holds per layer (raw/derived/node/deep) and lane (1min, 5min, hour, daily...).
Query bar windows: by series names/patterns (
btc_*,*_close) ormarkets+fields, with UTC start/end, a period (30d, 2m, 1y, all) or newest bars, up to 50,000 rows, resumable vianext_start.Get the latest bar of named series on a chosen layer and lane.
Take a live tick: every series the key holds on every lane at the just-closed boundary, in one answer.
Heal a kept copy: fetch every value corrected since a timestamp, chaining each answer's
until.Try before buying: free sample of each plan tier with real aligned values and links to full sample files.
Track budget: current plan, history days, limits and usage today.
Safe by design: all tools read-only and idempotent, no trading; only data tools need
TILLA_API_KEY.
Provides market data sourced from the author's own Bitcoin node, delivered on the same 1-minute UTC close-labelled clock as the rest of the TILLA feed (crypto, US stocks and ETFs, FX, indices, commodities, rates and macro), so an agent can pull on-chain/network-derived Bitcoin data alongside other series through the same tick, resume and heal calls.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
TILLA
Market data for trading models, bots and AI agents. Crypto, US stocks and ETFs, FX, rates and macro on one UTC clock, from 1-minute bars to quarterly.
Every market lines up. BTC, NVDA, EUR/USD, the 10-year yield and VIX share the same timestamp. No joins, no drift.
Bitcoin and Ether spot ETF flows, fund by fund, daily, next to price, funding and open interest.
280,675 derived indicators, computed bar by bar with no look-ahead.
Our own Bitcoin node: blocks, mempool and fees on the same clock as the market.
Your copy never breaks. Go offline and one call refills every missed bar; a second call delivers every value a source corrected later.
History: hourly crypto from 2017, FX from 2002.
Site: https://tillacrypto.com · Docs: https://tillacrypto.com/docs · Plans: https://tillacrypto.com/pricing
In your AI agent (MCP)
pip install tilla-mcp{
"mcpServers": {
"tilla": {
"command": "tilla-mcp",
"env": { "TILLA_API_KEY": "tk_live_your_key_here" }
}
}
}With uv there is nothing to install: "command": "uvx", "args": ["tilla-mcp"].
Or nothing to install at all - the hosted server: https://mcp.tillacrypto.com/mcp (streamable HTTP). Send your
key as the X-API-Key header (or Authorization: Bearer <key>, or ?key=<key>); the free tools answer without one.
{ "mcpServers": { "tilla": { "url": "https://mcp.tillacrypto.com/mcp", "headers": { "X-API-Key": "tk_live_..." } } } }14 tools for Claude, Cursor or any MCP client: latest bars, history, one whole market at a time, the live tick,
corrections and plans. Ask things like "BTC price against spot ETF flows this month" or "NVDA and BTC on one
hourly chart". Tool list: mcp/README.md.
Related MCP server: x402 crypto market structure
A key and a first call
A free key, no account and no card:
curl -X POST https://api.tillacrypto.com/v1/demo_keycurl -H "X-API-Key: tk_live_YOUR_KEY" "https://api.tillacrypto.com/v1/free/raw/1min?series=btc_close,eth_close&limit=5"Every bar is labelled by its close, in UTC. A value a source never published stays empty; nothing is guessed.
JSON, CSV, NDJSON or Parquet (format=). A Postman collection has every call ready to run.
What's in here
Folder | What it is |
| |
| |
a first call, every coin's close in one call, a day of data in pandas, | |
the API as a Postman collection; Insomnia and other clients import |
cd starter
python tilla_dashboard.py --keep tilla.dbThe three calls behind it
Tick -
GET /v1/<tier>/tick- every series your plan holds for the bar that just closed, in one answerResume -
GET /v1/<tier>/resume/<layer>/<lane>?since=...- every bar since you stopped, streamedChanges -
GET /v1/<tier>/changes?since=...- every value corrected since a time, so your copy gets the fix
Safe to run
Everything here only reads market data from api.tillacrypto.com over HTTPS. Nothing trades, touches a wallet or
reads your other files. Your key stays in your own .env or environment and goes only to the TILLA API. The only
thing written is the SQLite file you name with --keep.
License
The code is MIT (LICENSE). The data you pull with it is covered by your TILLA plan: https://tillacrypto.com/docs
Contact
I answer every message myself: https://tillacrypto.com/contact, @TillaCryptoHub on X, or an issue on this repo.
Available Tools
14 toolstilla_aboutAbout TILLAARead-onlyIdempotentInspect
What TILLA is, who it's for, and how to start. No API key needed.
Inputs: no named parameters.
tilla_changesCorrections since a timeARead-onlyIdempotentInspect
Every value our checks repaired since since ('YYYY-MM-DD HH:MM:SS') that the key holds, with its value now -
apply them and a kept copy stays correct. Pass the answer's until as the next since. Needs a key.
Inputs: since (required).
tilla_docsThe API manualARead-onlyIdempotentInspect
The whole API manual in one call, no key needed: every call, every parameter, every plan, how paging, tick, resume, changes and bulk work. Read this first when you need to know how to do anything.
Inputs: no named parameters.
tilla_healthIs every lane currentBRead-onlyIdempotentInspect
The newest bar of every lane on every layer - is the data current? No API key needed.
Inputs: no named parameters.
tilla_inventorySeries this key holdsARead-onlyIdempotentInspect
Exactly what the caller's key holds. No arguments: every lane per layer with its series count. layer=raw|derived|node and lane=1min|hour|daily|...: every series name there. Call this before tilla_latest / tilla_window and use the names it returns. Needs TILLA_API_KEY.
Inputs: lane, layer.
tilla_latestLatest barBRead-onlyIdempotentInspect
The newest bar of the named series on one lane. Needs TILLA_API_KEY.
Inputs: series (required), lane, layer.
tilla_marketOne whole marketARead-onlyIdempotentInspect
One market in one call: every series of market (an id from tilla_markets, e.g. btc, nvda, eurusd, gold) the
key holds on lane, on one clock. layer = raw | derived | node | deep | all. related=True adds its connected
markets (btc: its ETFs and miners). period = 1d 7d 30d 2m 3m 6m 1y 2y 3y all. At most 200 columns an answer:
series_next_offset names the next page. Needs TILLA_API_KEY.
Inputs: market (required), lane, layer, limit, +2 more.
tilla_marketsEvery marketARead-onlyIdempotentInspect
Every market TILLA carries - crypto, US stocks and ETFs, FX, macro - with its category, its related markets,
how many series each plan holds of it, and its lanes. No API key needed. Use the id with tilla_market.
Inputs: no named parameters.
tilla_sampleFree sample of a planARead-onlyIdempotentInspect
The free sample of one plan (free, builder, pro or max), no key needed: how many series it holds on every
lane, and one aligned 1-minute row of real values. The full one-tick files are at /v1/sample/.csv and
.db (named in the answer's files).
Inputs: tier.
tilla_statusFeed statusARead-onlyIdempotentInspect
The newest 1-minute bar and the tiers served. No API key needed.
Inputs: no named parameters.
tilla_tickEverything that just closedARead-onlyIdempotentInspect
Your whole plan, live, in one call: every series the key holds on every lane that closed at a boundary (at =
'YYYY-MM-DD HH:MM', default the minute just closed). Per lane: bar, complete, series, values. Needs a key.
Inputs: at, lanes.
tilla_tiersPlans and limitsARead-onlyIdempotentInspect
The public plans: price, history cap, request limits and size. No API key needed.
Inputs: no named parameters.
tilla_usagePlan and budgetARead-onlyIdempotentInspect
The caller's plan and budget right now: tier, history days, limits, used today. Needs TILLA_API_KEY.
Inputs: no named parameters.
tilla_windowBars in a time rangeARead-onlyIdempotentInspect
A window of bars. Name exactly what you want, one of: series = comma-separated names (at most 200) from
tilla_inventory, or a pattern like 'btc_*' / '*_close'; or markets + fields ('btc,eth' + 'close,volume' ->
btc_close, btc_volume, eth_close, eth_volume). layer = raw | derived | node | deep; lane = 1min, 5min, hour,
daily, ... start/end = 'YYYY-MM-DD[ HH:MM[:SS]]' UTC inclusive, or period = 30d 2m 6m 1y all; no start = the
newest bars. limit <= 50000. When more is true, call again with start = next_start. Needs TILLA_API_KEY.
Inputs: end, lane, layer, limit, +5 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools target clearly distinct resources or actions, and descriptions clarify boundaries well. There is some overlap between status/health for freshness checks and latest/window/tick for bar retrieval, but the intended use cases remain distinguishable.
Every tool uses the same tilla_ prefix with snake_case naming, giving a highly predictable and consistent namespace. The set does not mix camelCase, vague verbs, or inconsistent conventions.
Fourteen tools is well-scoped for a market data API, covering discovery, metadata, authentication context, and several bar retrieval modes. Each tool appears to earn its place without excessive surface area.
The surface covers discovery, plan/inventory inspection, market metadata, freshness checks, usage, and multiple data retrieval modes including paging and changes. Minor gaps exist around direct bulk file access or key management, but core read workflows are well covered.
Maintenance
Related MCP Connectors
Crypto market data for AI agents: live prices, OHLCV, sentiment, indicators and exchanges.
Macroeconomic and FX time-series data for AI agents: indicators, calendars, COT, forex, commodities.
Crypto market data for AI agents: top crypto pairs, derivatives, options, macro, on-chain.
Live crypto market data: prices, funding, OI, liquidations, regimes, GEX, whales, sentiment, macro.
Related MCP Servers
- AlicenseAqualityBmaintenancePoint-in-time market data for AI agents: stocks, ETFs and crypto as named bands plus raw values.105MIT
- AlicenseBqualityDmaintenanceCross-exchange crypto orderflow for AI agents. 20 exchanges, 26 tokens, 9 tools — CVD, whale activity, funding/OI, 7-year OHLCV, on-chain address risk (EVM + Solana). Pay-per-call USDC via x402, no API key.924 npm1MIT
- AlicenseNot gradedqualityCmaintenanceRead-only crypto perps microstructure for AI agents: normalized cross-exchange market state (funding + multi-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis), OHLCV, 15-min state history, and measured conditional outcomes (historical base rates, not predictions) — 6 assets across Binance, Bybit, OKX and Hyperliquid, every metric with self-declared coverage and freshnessMIT
- AlicenseBqualityFmaintenanceReal-time crypto, stock, and prediction-market data for agents — prices, indicators, funding rates, DeFi TVL, macro calendar, and an AI momentum score. Configure one Base wallet key and it just works. No signup, no dashboard, no subscription.22265 npmMIT