xyz.anansidata/anansi-data
REMOTE · ANANSIDATA.XYZ · SCANNED AUG 21
Time-series nobody else archives: LLM price history, prediction markets, gas, perp funding.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1706 tokens (~142/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 1 day we've observed: 12 tool removals, 0 breaking changes, 0 auth/transport breaks, 12 additions. See how to fix → Fail
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · anansidata.xyz
claude mcp add --transport http xyz-anansidata-anansi-data https://anansidata.xyz/mcp
[mcp_servers.xyz-anansidata-anansi-data] url = "https://anansidata.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-anansidata-anansi-data": {
"type": "remote",
"url": "https://anansidata.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-anansidata-anansi-data --url https://anansidata.xyz/mcp --transport streamable-http
mcp_servers:
xyz-anansidata-anansi-data:
url: "https://anansidata.xyz/mcp" {
"mcpServers": {
"xyz-anansidata-anansi-data": {
"type": "http",
"url": "https://anansidata.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Aug 26 +1
- Stability: unverified → fail ▼ security
- Tool “data_changes” was removed ▼ security
- Tool “data_history” was removed ▼ security
- Tool “data_latest” was removed ▼ security
- Tool “data_search” was removed ▼ security
- Tool “how_to_pay” was removed ▼ security
- Tool “intel_anomalies” was removed ▼ security
- Tool “intel_movers” was removed ▼ security
- Tool “intel_verdict” was removed ▼ security
- Tool “list_datasets” was removed ▼ security
- Tool “list_offerings” was removed ▼ security
- Tool “model_advisor” was removed ▼ security
- Tool “model_changes” was removed ▼ security
- Schema quality: pass → fail ▼ functional
- Schema quality: fair → good functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “anansi_anomalies” functional
- New tool “anansi_data_changes” functional
- New tool “anansi_data_history” functional
- New tool “anansi_data_latest” functional
- New tool “anansi_data_search” functional
- New tool “anansi_movers” functional
- New tool “anansi_price_advisor” functional
- New tool “anansi_price_changes” functional
- New tool “anansi_price_changes_recent” functional
- New tool “anansi_price_current” functional
- New tool “anansi_search” functional
- New tool “anansi_verdict” functional
- 20 Aug 26 56
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 21 Aug 2026 · Probed https://anansidata.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anansidata.xyz | CN=YE1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5d57eba3dccad758057166e667a8254d802 |
| SANs: anansidata.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of anansidata.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| anansidata.xyz. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://anansidata.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://anansidata.xyz/mcp | HTTPS enforced | 308 | https://anansidata.xyz/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.
anansi_anomalies ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| field | string | yes | – |
| payment_header | – | – | – |
| z_threshold | number | – | – |
No output schema declared.
No examples provided.
anansi_data_changes ~122
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 archive.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| payment_header | – | – | – |
| since | integer | – | – |
No output schema declared.
No examples provided.
anansi_data_history ~144
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. Inputs: dataset and key exactly as returned by anansi_search; since is a unix timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| key | string | yes | – |
| payment_header | – | – | – |
| since | integer | – | – |
No output schema declared.
No examples provided.
anansi_data_latest ~144
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_changes). Input: dataset must be an exact name from anansi_search; key optionally narrows to one row.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| key | string | – | – |
| payment_header | – | – | – |
No output schema declared.
No examples provided.
anansi_data_search ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| payment_header | – | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
anansi_movers ~138
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 is seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| field | string | yes | – |
| limit | integer | – | – |
| payment_header | – | – | – |
| window_s | integer | – | – |
No output schema declared.
No examples provided.
anansi_price_advisor ~185
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_price_current, free). Inputs: max_prompt_price in USD per token (e.g. 0.000001); min_context in tokens; modality is a substring of the modality string such as 'text' or 'image'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| max_prompt_price | – | – | – |
| min_context | integer | – | – |
| modality | string | – | – |
| payment_header | – | – | – |
| window_s | integer | – | – |
No output schema declared.
No examples provided.
anansi_price_changes ~131
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 that free. Input: since is a unix timestamp; omit it for everything we hold.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_header | – | – | – |
| since | integer | – | – |
No output schema declared.
No examples provided.
anansi_price_changes_recent ~160
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 vanished. Do NOT use it for windows longer than 7 days or more than 25 rows — it is capped; use anansi_price_changes (paid) for the full unwindowed history. Input: days is clamped to 7.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
anansi_price_current ~163
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 observation; use anansi_price_changes_recent (free) or anansi_price_history (paid). Input: model_id is a substring match, so 'gpt-5' matches every gpt-5 variant; resolve exact IDs with anansi_search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| model_id | string | – | – |
No output schema declared.
No examples provided.
anansi_search ~134
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 anansi_data_search (paid) to search every field of every dataset. Input: q is a case-insensitive substring.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
anansi_verdict ~146
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, key and a numeric field, all exactly as named in the dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| field | string | yes | – |
| key | string | yes | – |
| payment_header | – | – | – |
No output schema declared.
No examples provided.