io.github.atmflow55/datafood-mcp
REMOTE · TOUGHLOVESEC.WIN
DataFood: 16 data sources (crypto/DeFi/security/news/finance) via one MCP. Bundles save ~92%.
Available components
Last scanned (5 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 → Why this is hard to 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 4 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 445 tokens (~44/item across 10 items; 4 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://toughlovesec.win/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toughlovesec.win | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e93f6b9b081dd8767aa31460594b0f4161 |
| SANs: *.toughlovesec.win, toughlovesec.win | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of toughlovesec.win. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| win. | present | 29737 | 8 | Verified |
| toughlovesec.win. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://toughlovesec.win/mcp | Verified | 200 | |
| http (plaintext) | http://toughlovesec.win/mcp | HTTPS enforced | 301 | https://toughlovesec.win/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
datafood_bundle ~102
Bundle 1-20 cross-niche queries in one call. Saves 50-92% vs. per-API. Free preview accepts up to 5; paid via Stripe session_id or x402 X-Payment header.
| Name | Type | Req | Description |
|---|---|---|---|
| free | boolean | – | If true, return free 1-row preview (capped at 5 queries) |
| queries | array | yes | – |
| session_id | string | – | Optional Stripe checkout session_id for paid full results |
No output schema declared.
No examples provided.
datafood_portfolio_ask ~64
Natural-language Q&A on a Plaid-linked portfolio (read-only). Requires user_id of a previously-synced portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | e.g. 'Am I overexposed to tech?' |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
datafood_query ~81
Fetch a single data type from DataFood. Free 1-row preview, no auth required. Use datafood_bundle for 3+ queries (cheaper).
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Query string. See /api/v1/catalog for per-type examples. |
| type | string | yes | One of 42 supported data types (DATAFOOD_CATALOG) |
No output schema declared.
No examples provided.
datafood_watch_session ~60
Open a watchable agent session — returns session_id and a public /watch/{id} URL for live observation. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Optional human-readable agent identifier |
| intent | string | – | Optional one-line intent string |
No output schema declared.
No examples provided.
How do I install the io.github.atmflow55/datafood-mcp server?
io.github.atmflow55/datafood-mcp is a hosted endpoint at https://toughlovesec.win/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · toughlovesec.win
claude mcp add --transport http atmflow55-datafood-mcp 'https://toughlovesec.win/mcp'
What is the io.github.atmflow55/datafood-mcp server?
io.github.atmflow55/datafood-mcp is listed in the public MCP registry as io.github.atmflow55/datafood-mcp. DataFood: 16 data sources (crypto/DeFi/security/news/finance) via one MCP. Bundles save ~92%. This page covers its hosted endpoint (https://toughlovesec.win/mcp).
Is the io.github.atmflow55/datafood-mcp server safe to use?
io.github.atmflow55/datafood-mcp scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.atmflow55/datafood-mcp server expose?
io.github.atmflow55/datafood-mcp exposes 4 tools: datafood_query, datafood_bundle, datafood_portfolio_ask, datafood_watch_session. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.
Does the io.github.atmflow55/datafood-mcp server require authentication?
No. We connected to io.github.atmflow55/datafood-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.atmflow55/datafood-mcp server still maintained?
io.github.atmflow55/datafood-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.