Ext Ops Panel
Open dashboard
Comparison

TILLA - market data on one clock vs AuraStream

TILLA - market data on one clock is an MCP server published by TillaCrypto. Marketplaces we read that list it: 1 (Official MCP Registry). AuraStream is an MCP server published by UnbiasedAlpha. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceTILLA - market data on one clockAuraStream
Official MCP Registry Listed
Version: 2.0.3
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.7
Downloads/month (PyPI): 0
Downloads/week (PyPI): 307
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

TILLA - market data on one clock vs AuraStream
FactTILLA - market data on one clockAuraStream
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-11-04 (better)2026-10-27 (worse)
Where it runs (differs)Remote server (mcp.tillacrypto.com/mcp)On your machine (aurastream-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 13, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/tillacrypto/tillagithub.com/unbiasedalpha/aurastream-mcp
Changes in the last 7 days (differs)50
First seen (differs)2026-10-312026-10-26
Endpoint at the last check (differs)Status out of date: last check 46 h ago returned HTTP 406no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

TILLA - market data on one clock

In its own words, on Official MCP Registry:

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

AuraStream

In its own words, on Official MCP Registry:

Historical market, macro, positioning and alt data from 45 sources through one API.

How to run each

TILLA - market data on one clock As a remote MCP server

Claude Code
claude mcp add --transport http tilla-mcp https://mcp.tillacrypto.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: TILLA_API_KEY (secret), X-API-Key header

AuraStream As a local MCP server: PyPI package

Claude Code
claude mcp add --env "AURASTREAM_API_KEY=<YOUR_AURASTREAM_API_KEY>" --env "FRED_API_KEY=<YOUR_FRED_API_KEY>" --env "NEMETON_API_KEY=<YOUR_NEMETON_API_KEY>" --transport stdio aurastream-mcp -- uvx aurastream-mcp

Requires: AURASTREAM_API_KEY (secret), FRED_API_KEY (secret), NEMETON_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only TILLA - market data on one clock has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only TILLA - market data on one clock asks for

  • TILLA_API_BASE
  • TILLA_API_KEY (secret)

Only AuraStream asks for

  • AURASTREAM_API_KEY (secret)
  • FRED_API_KEY (secret)
  • NEMETON_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: TILLA - market data on one clock · What it can do: AuraStream · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built