mcp-registry/io.github.atmflow55/datafood-mcp · v6.0.0
Also listed as glama/atmflow55/datafood
As of 2026-10-18 05:19 UTC, the Atmflow55 Datafood MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 47 outages in 90 days, with a median recovery of 7 minutes.
DataFood: 16 data sources (crypto/DeFi/security/news/finance) via one MCP. Bundles save ~92%.
Claude Code
claude mcp add --transport http atmflow55-datafood-mcp-server https://toughlovesec.win/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"atmflow55-datafood-mcp-server": {
"type": "http",
"url": "https://toughlovesec.win/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 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 →
2 parameter(s) across 2 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 →
Handshake + tools/list takes ~2,548 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp/fixes
{
"name": "datafood_query",
"description": "Fetch a single data type from DataFood. Free 1-row preview, no auth required. Use datafood_bundle for 3+ queries (cheaper).",
"inputSchema": {
"type": "object",
"required": [
"type"
],
"properties": {
"q": {
"type": "string",
"description": "Query string. See /api/v1/catalog for per-type examples."
},
"type": {
"enum": [
"token-risk",
"breach",
"contract-risk",
"defi-yield",
"scrape",
"crypto-price",
"crypto-trending",
"stock-quote",
"weather",
"news-hn-top",
"news-reddit",
"flights-near",
"real-estate-rss",
"sports-scores",
"gas-prices-eth",
"forex",
"github-trending",
"whale-tracker",
"liquidations",
"funding-rates",
"order-book",
"ta-indicators",
"sentiment-ticker",
"token-unlock",
"mev-exposure",
"stable-depeg",
"cross-dex-arb",
"energy-oil",
"energy-grid-eu",
"shipping-bdi",
"air-quality",
"cdc-flu",
"who-outbreak",
"sec-edgar",
"acled-conflict",
"gdelt-events",
"twitch-top",
"steam-top",
"reddit-trending",
"commodity-metals",
"agriculture-prices",
"legal-courtlistener",
"economic-indicator"
],
"type": "string",
"description": "One of 42 supported data types (DATAFOOD_CATALOG)"
}
}
},
"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/io.github.atmflow55/datafood-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.atmflow55/datafood-mcp"}) over MCP.
datafood_bundle ~358 tokensdatafood_query ~299 tokensdatafood_watch_session ~102 tokensdatafood_portfolio_ask ~97 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.atmflow55%2Fdatafood-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7531d25eb834c1f5…, first seen 2026-10-17, included at leaf 10689 of 20,444. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable other 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
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 05:19 UTC, the Atmflow55 Datafood MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 47 outages in 90 days, with a median recovery of 7 minutes.
Atmflow55 Datafood MCP server advertises 4 tools, including datafood_bundle, datafood_portfolio_ask, datafood_query, datafood_watch_session.
Point your MCP client at this streamable-http endpoint: https://toughlovesec.win/mcp
Glimind scanned all 4 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.