TILLA - market data on one clock MCP server
io.github.TillaCrypto/tilla-mcpTillaCryptostreamable-httpv2.0.3Scanned
Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted.
14 tools: 13 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 14
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
13 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TILLA - market data on one clock MCP server can do
The TILLA - market data on one clock MCP server is published by the GitHub account TillaCrypto. It has 14 tools. It can create or change data (13 tools: tilla_about, tilla_tiers, tilla_inventory, tilla_window and 9 more), but cannot delete data. 1 tool only reads.
14 tools bring in text other people can write (tilla_about, tilla_status, tilla_tiers and 11 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 2.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Changes things 13Claude Code: ask
tilla_aboutWhat TILLA is, who it's for, and how to start.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it What TILLA is, who it's for, and how to start. No API key needed.
Annotations the server declares
- title: About TILLA
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_changesEvery 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Corrections since a time
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_docsThe whole API manual in one call, no key needed: every call, every parameter, every plan, how paging, tick, resume, changes and bulk work.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: The API manual
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_healthThe newest bar of every lane on every layer - is the data current?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The newest bar of every lane on every layer - is the data current? No API key needed.
Annotations the server declares
- title: Is every lane current
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_inventoryExactly what the caller's key holds.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
Annotations the server declares
- title: Series this key holds
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_latestThe newest bar of the named series on one lane.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The newest bar of the named series on one lane. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
Annotations the server declares
- title: Latest bar
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_marketOne market in one call: every series of `market` (an id from tilla_markets, e.g.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
Annotations the server declares
- title: One whole market
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_marketsEvery 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Every market
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_sampleThe 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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`).
Annotations the server declares
- title: Free sample of a plan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_tickYour 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).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Everything that just closed
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_tiersThe public plans: price, history cap, request limits and size.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The public plans: price, history cap, request limits and size. No API key needed.
Annotations the server declares
- title: Plans and limits
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_usageThe caller's plan and budget right now: tier, history days, limits, used today.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The caller's plan and budget right now: tier, history days, limits, used today. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
Annotations the server declares
- title: Plan and budget
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tilla_windowA window of bars.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
Annotations the server declares
- title: Bars in a time range
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
tilla_statusThe newest 1-minute bar and the tiers served.Reads text others writeNo findings
Why it is in this group
- The name "tilla_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The newest 1-minute bar and the tiers served. No API key needed.
Annotations the server declares
- title: Feed status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write14
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 530
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 530.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:tilla_inventoryChanges thingsdescription
- Changed:tilla_latestChanges thingsdescription
- Changed:tilla_marketChanges thingsdescription
- Changed:tilla_usageChanges thingsdescription
- Changed:tilla_windowChanges thingsdescription
Install
Pinned to version 2.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http tilla https://mcp.tillacrypto.com/mcpclaude mcp add --transport http tilla https://mcp.tillacrypto.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tilla__tilla_status"
],
"ask": [
"mcp__tilla__tilla_about",
"mcp__tilla__tilla_tiers",
"mcp__tilla__tilla_inventory",
"mcp__tilla__tilla_window",
"mcp__tilla__tilla_latest",
"mcp__tilla__tilla_usage",
"mcp__tilla__tilla_markets",
"mcp__tilla__tilla_market",
"mcp__tilla__tilla_sample",
"mcp__tilla__tilla_health",
"mcp__tilla__tilla_docs",
"mcp__tilla__tilla_tick",
"mcp__tilla__tilla_changes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tilla. Review it before you use it.
Capability tags behind 14 rules
- mcp__tilla__tilla_about untrusted-input
- mcp__tilla__tilla_status untrusted-input
- mcp__tilla__tilla_tiers untrusted-input
- mcp__tilla__tilla_inventory untrusted-input
- mcp__tilla__tilla_window untrusted-input
- mcp__tilla__tilla_latest untrusted-input
- mcp__tilla__tilla_usage untrusted-input
- mcp__tilla__tilla_markets untrusted-input
- mcp__tilla__tilla_market untrusted-input
- mcp__tilla__tilla_sample untrusted-input
- mcp__tilla__tilla_health untrusted-input
- mcp__tilla__tilla_docs untrusted-input
- mcp__tilla__tilla_tick untrusted-input
- mcp__tilla__tilla_changes untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.TillaCrypto/tilla-mcp/verify?hash=ff9352c37d15d6b2d7415308ad7b28f777cc75d3bb3e516a90605f2b80a1bb5a" | jq -e '.changed == false'Pinned hash ff9352c37d15, from Nov 18, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.TillaCrypto/tilla-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.TillaCrypto/tilla-mcp)Source: MCP Registry · repository. Synced Nov 4, 2026, 22:18 UTC.
TILLA - market data on one clock MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TILLA - market data on one clock MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TILLA - market data on one clock MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TILLA - market data on one clock MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TILLA - market data on one clock MCP server have?
- 14 tools: 13 write, 1 read. tilla_about, tilla_tiers, tilla_inventory, tilla_window, tilla_latest, tilla_usage, tilla_markets, tilla_market and 6 more.
Does the TILLA - market data on one clock MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the TILLA - market data on one clock MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TILLA - market data on one clock MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.