
Anansi Data MCP server
Which MCP servers are Anansi Data's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namexyz.anansidata/anansi-dataverified in the MCP registry
The registry name sits under anansidata.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools12
- Server calls itselfanansi-data
- Server version1.2.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 86 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 12 of 12 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer322 ms
- Space in an agent's context≈ 2,529 tokensthe definitions of all its tools (12), which an agent carries on every turn
- Tool definitionsC · 67 of 100
- Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 12 of 12
- Not saying whether it only reads or can destroy: 12 of 12
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
anansi_searchFREE. 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'…
anansi_price_currentFREE. 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…
anansi_price_changes_recentFREE. 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…
anansi_price_changesPAID ($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…
anansi_price_advisorPAID ($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…
anansi_data_latestPAID ($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…
anansi_data_historyPAID ($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_changesPAID ($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…
anansi_data_searchPAID ($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…
anansi_moversPAID ($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…
anansi_anomaliesPAID ($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_verdictPAID ($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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"anansi-data": {
"type": "http",
"url": "https://anansidata.xyz/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http anansidata https://anansidata.xyz/mcpclaude.ai, ChatGPT and other clients: add https://anansidata.xyz/mcp as a custom connector in the settings.
OpenAPI spec
29 paths, read 2026-10-26. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.