Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Anansi Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Time-series nobody else archives: LLM price history, prediction markets, gas, perp funding.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http anansi-data-mcp https://anansidata.xyz/mcp
# 2 — ask your agent for something these tools do
# anansi_search, anansi_price_current, anansi_price_changes_recent and 9 more
Anansi Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http anansi-data-mcp https://anansidata.xyz/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
FREE. Resolves a partial name into exact model IDs and dataset names you can pass to the other tools; returns two string arrays (models, datasets), capped at 25 each. Use this FIRST whenever you have a fuzzy name like 'deepseek' or 'gas' and need the canonical identifier. Do NOT use it to retrieve values or search inside records — it matches names only; use anansi_price_current for prices or anans
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | — |
| limit | integer | no | — |
FREE. Current per-token prices for LLMs as recorded at our last poll: usd_per_prompt_token and usd_per_completion_token (USD per single token, not per million), context window in tokens, and the observation timestamp (unix seconds). Use this to check what a model costs right now, or to compare a handful of models before routing. Do NOT use it to see how a price MOVED — it returns only the latest o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model_id | string | no | — |
| limit | integer | no | — |
FREE. LLM price changes we observed in the last 7 days: per model, which field moved (prompt, completion, cache_read), the from/to values in USD per token, the percentage move, and the unix timestamp we detected it. Providers publish only their current catalogue and overwrite it silently, so this record exists nowhere upstream. Use it to detect that a model you depend on got cheaper, dearer, or va
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| limit | integer | no | — |
PAID ($0.03 via x402). The COMPLETE observed price-change history for every tracked LLM, with no time window and no row cap: model, field, from/to in USD per token, percent move, and detection timestamp. Use it to audit a provider's pricing behaviour over the whole archive or to feed a cost model. Do NOT use it for a quick 'did anything change lately' check — anansi_price_changes_recent answers th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | integer | no | — |
| payment_header | no | — |
PAID ($0.05 via x402). Answers 'which model should I route to' in one call: returns the cheapest models satisfying hard constraints on price, context window and modality, ranked by prompt price ascending, PLUS every price change and deprecation affecting those candidates in the window. Use it when choosing or re-validating a routing target. Do NOT use it merely to look up one model's price (anansi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_prompt_price | no | — | |
| min_context | integer | no | — |
| modality | string | no | — |
| window_s | integer | no | — |
| limit | integer | no | — |
| payment_header | no | — |
PAID ($0.005 via x402). Current state of every tracked key in one dataset, as recorded at our last poll, with provenance naming the source and licence. Use it for the newest snapshot of a whole dataset — prediction-market probabilities, gas by chain, perp funding, stablecoin pegs. Do NOT use it for LLM prices (anansi_price_current is free) and do NOT use it for change-over-time (anansi_data_change
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| key | string | no | — |
| payment_header | no | — |
PAID ($0.02 via x402). The full recorded time-series for ONE key in one dataset, oldest to newest, each row carrying its observation timestamp. Use it to chart or backtest a single series. Do NOT use it to compare many keys at once (anansi_data_latest returns them all for one moment) and do NOT expect history predating our first observation — the archive is days old and depth varies by dataset. In
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| key | string | yes | — |
| since | integer | no | — |
| payment_header | no | — |
PAID ($0.02 via x402). Field-level diffs across a whole dataset: for each key that changed, which field moved, its from and to values, and when. Use it to detect movement across many keys without pulling every series. Do NOT use it for LLM prices specifically — anansi_price_changes_recent is free and anansi_price_changes is the full version. Input: since is a unix timestamp; omit for the whole arc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| since | integer | no | — |
| payment_header | no | — |
PAID ($0.01 via x402). Full-text search across the CURRENT state of every sellable dataset at once, returning matching rows with their dataset name. Use it when you do not know which dataset holds a value. Do NOT use it to resolve a name to an identifier — anansi_search does that free — and note it searches current state only, not history. Input: q is a phrase match.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | — |
| limit | integer | no | — |
| payment_header | no | — |
PAID ($0.03 via x402). Velocity ranking: which keys in a dataset moved fastest on one numeric field over a window, returned as rate of change with the underlying from/to values. Use it to find what is moving without reading every series. Do NOT use it to judge whether a move is unusual for that key — that is anansi_anomalies. Inputs: field must be a numeric field present in the dataset; window_s i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| field | string | yes | — |
| window_s | integer | no | — |
| limit | integer | no | — |
| payment_header | no | — |
PAID ($0.05 via x402). Statistical outliers: keys whose latest move breaks their OWN historical baseline, returned with a z-score. Use it to separate a genuinely abnormal move from ordinary volatility. Do NOT use it to rank raw speed (anansi_movers) and treat results cautiously on a young dataset, where a short baseline inflates z-scores. Input: z_threshold defaults to 3.0.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| field | string | yes | — |
| z_threshold | number | no | — |
| payment_header | no | — |
PAID ($0.04 via x402). One-call composite for a single key: its latest value, its velocity, its rank against peers in the same dataset, and its anomaly z-score — the answer four separate calls would give. Use it when you have one specific key and want a verdict rather than raw series. Do NOT use it to survey many keys (anansi_movers) or to fetch a full series (anansi_data_history). Inputs: dataset
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | — |
| key | string | yes | — |
| field | string | yes | — |
| payment_header | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Anansi Data or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Anansi Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.