TILLA - market data on one clock is answering right now. Last checked 2 min ago. 1 094 installs a week from pypi. It exposes 14 tools. Last commit 1 Nov 2026.
Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted.
Installs per day
peak 686 · avg 36
a month agotoday
Uptime history
20 hours of history · worst hour 0%
20 hours agonow
77.8%
Uptime 24h
56 of 72 checks
14
Tools
read from the server
513 ms
Response time
average over 24h
1 094
Installs / week
npm and PyPI
TILLA - market data on one clock does not always answer
Over the last week it answered 77.8% 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 2 min ago.
run in your terminal
claude mcp add tilla-mcp --transport http https://mcp.tillacrypto.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.tillacrypto.com/mcp~/.codex/config.toml
[mcp_servers.tilla-mcp]
url = "https://mcp.tillacrypto.com/mcp".cursor/mcp.json
{
"mcpServers": {
"tilla-mcp": {
"url": "https://mcp.tillacrypto.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"tilla-mcp": {
"type": "http",
"url": "https://mcp.tillacrypto.com/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
tilla
tilla_about
What TILLA is, who it's for, and how to start. No API key needed.
tilla_changes
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.
tilla_docs
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.
tilla_health
The newest bar of every lane on every layer - is the data current? No API key needed.
tilla_inventory
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.
tilla_latest
The newest bar of the named series on one lane. Needs TILLA_API_KEY.
tilla_market
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.
tilla_markets
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.
tilla_sample
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/<tier>.csv and
.db (named in the answer's `files`).
tilla_status
The newest 1-minute bar and the tiers served. No API key needed.
tilla_tick
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.
tilla_tiers
The public plans: price, history cap, request limits and size. No API key needed.
tilla_usage
The caller's plan and budget right now: tier, history days, limits, used today. Needs TILLA_API_KEY.
tilla_window
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.tillacrypto.com/mcp | streamable-http | answering | 455 ms | 2 min ago |
Alternatives to TILLA - market data on one clock
same job, measured the same wayFinance MCP
by adityasbisht
Live stock, crypto, SEC filings, FX and macro data for LLM agents. No API keys.
Finance MCP
by adididitagain
Live stock, crypto, SEC filings, insider trades, FX and macro data for LLM agents.
Market Data
by marketcrew
Live market data & technical analysis for US stocks, ETFs and crypto. Read-only, no signup.
santyvv-data — market & on-chain data
by santyvv
Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).
Tickscope
by seungdori
Real-time, free crypto market data for any AI agent — via MCP.
AssetFeed Market Data
by assetfeed
Read-only mention counts, recaps and market data for crypto, stocks, ETFs, forex and commodities.
OpenFinance — Easy Trading: Crypto, Stocks, Perps & Prediction Markets
by openfinance
Easy trading for AI agents: crypto, perps, stocks, prediction markets, forex and memecoins. One URL.
Coinversaa
by coinversaa
Crypto intelligence for AI agents. Hyperliquid trader analytics, cohorts, and live market data.
TILLA - market data on one clock — questions
Answers built from our own checks of this server.
What can TILLA - market data on one clock do?
It exposes 14 tools, read directly from the server on our last check. Among them: tilla_about, tilla_changes, tilla_docs, tilla_health, tilla_inventory, tilla_latest and 8 more. 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 TILLA - market data on one clock working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 56 of 72 checks got a reply (77.8%), average response time 513 ms. The bar chart above shows every period we have measured.
How do I connect TILLA - market data on one clock?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TILLA - market data on one clock need an API key?
No. TILLA - market data on one clock completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TILLA - market data on one clock?
It answers our handshake in 513 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use TILLA - market data on one clock?
The pypi package tilla-mcp was installed 1 094 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is TILLA - market data on one clock open source?
The code is open source: it is published under the MIT licence, written in Python and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.tillacrypto.com, which runs on its operator's own terms.