# TILLA - market data on one clock (pypi · tilla-mcp)

Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.tillacrypto.com`: 70/100, [markdown](https://verifymcp.io/servers/tillacrypto-tilla-mcp/mcp.md), [page](https://verifymcp.io/servers/tillacrypto-tilla-mcp/mcp)
- pypi · `tilla-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp.md), [page](https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp)

## Channel facts

- Registry: `pypi`
- Package: `tilla-mcp`
- Version: `2.0.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TillaCrypto/tilla).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1390 tokens (~86/item across 16 items; 14 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TILLA - market data on one clock MCP server?

TILLA - market data on one clock runs locally as a PyPI package, launched with uvx tilla-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add tillacrypto-tilla-mcp -- uvx tilla-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tillacrypto-tilla-mcp": {
      "command": "uvx",
      "args": [
        "tilla-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tillacrypto-tilla-mcp": {
      "command": "uvx",
      "args": [
        "tilla-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tillacrypto-tilla-mcp -- uvx tilla-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tillacrypto-tilla-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "tilla-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tillacrypto-tilla-mcp --command uvx --arg tilla-mcp
```

### Hermes

```yaml
mcp_servers:
  tillacrypto-tilla-mcp:
    command: "uvx"
    args: ["tilla-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tillacrypto-tilla-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "tilla-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tillacrypto-tilla-mcp -t stdio -c uvx -a tilla-mcp
```

### Other

```json
{
  "mcpServers": {
    "tillacrypto-tilla-mcp": {
      "command": "uvx",
      "args": [
        "tilla-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 65, −15)

- [security regression] Stability: 0.10 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] Package version: 2.0.2 → 2.0.3

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 2.0.1 → 2.0.2

### 2026-10-31 (score 78)

First indexed and scored.

## MCP tools (14)

### `tilla_about` (~28 tokens)

About TILLA

What TILLA is, who it's for, and how to start. No API key needed.

### `tilla_status` (~25 tokens)

Feed status

The newest 1-minute bar and the tiers served. No API key needed.

### `tilla_tiers` (~29 tokens)

Plans and limits

The public plans: price, history cap, request limits and size. No API key needed.

### `tilla_inventory` (~104 tokens)

Series this key holds

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).

Input parameters:

- `lane`
- `layer`

### `tilla_window` (~257 tokens)

Bars in a time range

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).

Input parameters:

- `end`
- `fields` (string)
- `lane` (string)
- `layer` (string)
- `limit` (integer)
- `markets` (string)
- `period`
- `series` (string)
- `start`

### `tilla_latest` (~63 tokens)

Latest bar

The newest bar of the named series on one lane. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).

Input parameters:

- `lane` (string)
- `layer` (string)
- `series` (string, required)

### `tilla_usage` (~50 tokens)

Plan and budget

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).

### `tilla_markets` (~63 tokens)

Every market

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_market` (~193 tokens)

One whole 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 your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).

Input parameters:

- `lane` (string)
- `layer` (string)
- `limit` (integer)
- `market` (string, required)
- `period`
- `related` (boolean)

### `tilla_sample` (~85 tokens)

Free sample of a plan

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`).

Input parameters:

- `tier` (string)

### `tilla_health` (~29 tokens)

Is every lane current

The newest bar of every lane on every layer - is the data current? No API key needed.

### `tilla_docs` (~55 tokens)

The API manual

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_tick` (~75 tokens)

Everything that just closed

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.

Input parameters:

- `at`
- `lanes`

### `tilla_changes` (~70 tokens)

Corrections since a time

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.

Input parameters:

- `since` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78

## Common questions

### 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 PyPI package (tilla-mcp).

### Is the TILLA - market data on one clock MCP server safe to use?

TILLA - market data on one clock scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.

### 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.

### What licence is the TILLA - market data on one clock MCP server under?

TILLA - market data on one clock declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/tilla-mcp/
- Socket report: https://socket.dev/pypi/package/tilla-mcp
- Repository: https://github.com/TillaCrypto/tilla
- Website: https://tillacrypto.com/
- Changelog RSS feed: https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tillacrypto-tilla-mcp/tilla-mcp