Skip to content

anansi-data MCP server

xyz.anansidata/anansi-dataanansidata.xyzstreamable-httpv1.1.0Scanned

Time-series nobody else archives: LLM price history, prediction markets, gas, perp funding.

12 tools: 10 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 10 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

10 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the anansi-data MCP server can do

The anansi-data MCP server is published by anansidata.xyz, a domain the MCP Registry verified. It has 12 tools. It can create or change data (10 tools: anansi_price_current, anansi_price_changes_recent, anansi_price_changes, anansi_price_advisor and 6 more), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 10Claude Code: ask
  • anansi_anomaliesPAID ($0.05 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_data_changesPAID ($0.02 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_data_historyPAID ($0.02 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_data_latestPAID ($0.005 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_moversPAID ($0.03 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_price_advisorPAID ($0.05 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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'.
  • anansi_price_changesPAID ($0.03 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_price_changes_recentFREE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_price_currentFREE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anansi_verdictPAID ($0.04 via x402).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://anansidata.xyz/mcp: tools/list returned 12 tools to an anonymous client, including anansi_price_current (write), anansi_price_changes_recent (write), anansi_price_changes (write), anansi_price_advisor (write), anansi_data_latest (write) and 5 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http anansi-data https://anansidata.xyz/mcp
claude mcp add --transport http anansi-data https://anansidata.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__anansi-data__anansi_search",
      "mcp__anansi-data__anansi_data_search"
    ],
    "ask": [
      "mcp__anansi-data__anansi_price_current",
      "mcp__anansi-data__anansi_price_changes_recent",
      "mcp__anansi-data__anansi_price_changes",
      "mcp__anansi-data__anansi_price_advisor",
      "mcp__anansi-data__anansi_data_latest",
      "mcp__anansi-data__anansi_data_history",
      "mcp__anansi-data__anansi_data_changes",
      "mcp__anansi-data__anansi_movers",
      "mcp__anansi-data__anansi_anomalies",
      "mcp__anansi-data__anansi_verdict"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as anansi-data. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.anansidata/anansi-data/verify?hash=5923b49a5df7d586ad199f65ca7861be81b4ebc5f4dc25ddb1e805a92b59e8d1" | jq -e '.changed == false'

Pinned hash 5923b49a5df7, from Nov 19, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.anansidata/anansi-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.anansidata/anansi-data
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.anansidata/anansi-data.svg)](https://radar.anlyon.com/servers/xyz.anansidata/anansi-data)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

anansi-data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the anansi-data MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the anansi-data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the anansi-data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the anansi-data MCP server have?

12 tools: 10 write, 2 read. anansi_price_current, anansi_price_changes_recent, anansi_price_changes, anansi_price_advisor, anansi_data_latest, anansi_data_history, anansi_data_changes, anansi_movers and 4 more.

Does the anansi-data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the anansi-data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the anansi-data MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.