TILLA - market data on one clock
REMOTE · MCP.TILLACRYPTO.COM · 2 COMPONENTS
Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted.
Available components
Last scanned (6 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1390 tokens (~86/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +47
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.13 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 4 Nov 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- Tool “tilla_latest” rewrote its description, which is the text the model reads security
- Tool “tilla_usage” rewrote its description, which is the text the model reads security
- Tool “tilla_window” rewrote its description, which is the text the model reads security
- Tool “tilla_inventory” rewrote its description, which is the text the model reads security
- Tool “tilla_market” rewrote its description, which is the text the model reads security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 2 Nov 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 1 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.tillacrypto.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tillacrypto.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b9d908723ab84397137fd2ae2f361159 |
| SANs: tillacrypto.com, *.tillacrypto.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tillacrypto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tillacrypto.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tillacrypto.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tillacrypto.com/mcp | HTTPS enforced | 301 | https://mcp.tillacrypto.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tilla_about About TILLA ~28
What TILLA is, who it's for, and how to start. No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_changes Corrections since a time ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | – |
No output schema declared.
No examples provided.
tilla_docs The API manual ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_health Is every lane current ~29
The newest bar of every lane on every layer - is the data current? No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_inventory Series this key holds ~104
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lane | – | – | – |
| layer | – | – | – |
No output schema declared.
No examples provided.
tilla_latest Latest bar ~63
The newest bar of the named series on one lane. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| lane | string | – | – |
| layer | string | – | – |
| series | string | yes | – |
No output schema declared.
No examples provided.
tilla_market One whole market ~193
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lane | string | – | – |
| layer | string | – | – |
| limit | integer | – | – |
| market | string | yes | – |
| period | – | – | – |
| related | boolean | – | – |
No output schema declared.
No examples provided.
tilla_markets Every market ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_sample Free sample of a plan ~85
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| tier | string | – | – |
No output schema declared.
No examples provided.
tilla_status Feed status ~25
The newest 1-minute bar and the tiers served. No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_tick Everything that just closed ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| at | – | – | – |
| lanes | – | – | – |
No output schema declared.
No examples provided.
tilla_tiers Plans and limits ~29
The public plans: price, history cap, request limits and size. No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_usage Plan and budget ~50
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tilla_window Bars in a time range ~257
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).
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| fields | string | – | – |
| lane | string | – | – |
| layer | string | – | – |
| limit | integer | – | – |
| markets | string | – | – |
| period | – | – | – |
| series | string | – | – |
| start | – | – | – |
No output schema declared.
No examples provided.
How do I install the TILLA - market data on one clock MCP server?
TILLA - market data on one clock is a hosted endpoint at https://mcp.tillacrypto.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tillacrypto.com
claude mcp add --transport http tillacrypto-tilla-mcp 'https://mcp.tillacrypto.com/mcp'
What is the TILLA - market data on one clock MCP server?
TILLA - market data on one clock is an MCP server listed in the public MCP registry as io.github.TillaCrypto/tilla-mcp. Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted. This page covers its hosted endpoint (https://mcp.tillacrypto.com/mcp).
Is the TILLA - market data on one clock MCP server safe to use?
TILLA - market data on one clock scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TILLA - market data on one clock MCP server expose?
TILLA - market data on one clock exposes 14 tools: tilla_about, tilla_status, tilla_tiers, tilla_inventory, tilla_window, and 9 more. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Does the TILLA - market data on one clock MCP server require authentication?
No. We connected to TILLA - market data on one clock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TILLA - market data on one clock MCP server still maintained?
TILLA - market data on one clock is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.