mcp-registry/xyz.anansidata/anansi-data · registry v1.1.0 · server reports v1.2.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:52 UTC, the Anansidata Anansi Data MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 5 minutes.
Time-series nobody else archives: LLM price history, prediction markets, gas, perp funding.
Point your MCP client at this streamable-http endpoint: https://anansidata.xyz/mcp
40 parameter(s) across 12 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.anansidata%2Fanansi-data/fixes
{
"name": "anansi_data_search",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "anansi_data_searchArguments",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"title": "Q"
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 20
},
"payment_header": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Payment Header",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "anansi_movers",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "anansi_moversArguments",
"required": [
"dataset",
"field"
],
"properties": {
"field": {
"type": "string",
"title": "Field"
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 20
},
"dataset": {
"type": "string",
"title": "Dataset"
},
"window_s": {
"type": "integer",
"title": "Window S",
"default": 604800
},
"payment_header": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Payment Header",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "anansi_search",
"description": "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 substrin",
"inputSchema": {
"type": "object",
"title": "anansi_searchArguments",
"properties": {
"q": {
"type": "string",
"title": "Q",
"default": ""
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.anansidata/anansi-data"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.anansidata/anansi-data"}) over MCP.
anansi_price_advisor ~305 tokensanansi_data_history ~248 tokensanansi_movers ~244 tokensanansi_verdict ~237 tokensanansi_data_latest ~236 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fxyz.anansidata%2Fanansi-data?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.anansidata%2Fanansi-data?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fxyz.anansidata%2Fanansi-data.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d77067e498738025…, first seen 2026-10-17, included at leaf 58 of 384,788. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:52 UTC, the Anansidata Anansi Data MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 5 minutes.
Anansidata Anansi Data MCP server advertises 12 tools, including anansi_anomalies, anansi_data_changes, anansi_data_history, anansi_data_latest, anansi_data_search.
Point your MCP client at this streamable-http endpoint: https://anansidata.xyz/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.