The Data Collector
REMOTE · FROG03-20494.WYKR.ES
Search Hacker News, Bluesky, and Substack from a single MCP interface
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 500, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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
- 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
- 9 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 8 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Stability: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Tool “list_scrapers” was removed ▼ security
- Tool “run_scraper” was removed ▼ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: web-data-labs → the-data-collector security
- Tool “bluesky_search” rewrote its description, which is the text the model reads security
- Tool “hn_search” rewrote its description, which is the text the model reads security
- Tool “substack_search” rewrote its description, which is the text the model reads security
- MCP protocol: unverified → fail ▼ functional
- “bluesky_search” added a required parameter “searchQuery”, so existing callers break ▼ functional
- “hn_search” added a required parameter “searchTerms”, so existing callers break ▼ functional
- “substack_search” added a required parameter “publications”, so existing callers break ▼ functional
- “bluesky_search” dropped the required parameter “query” ▼ functional
- “hn_search” dropped the required parameter “query” ▼ functional
- “substack_search” dropped the required parameter “query” ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: 92% → 100% ▲ functional
- Schema quality: 108 → 64 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: excellent → fair functional
- MCP protocol version: 2025-06-18 → 2024-11-05 functional
- Server version: 2.0.0 → 1.2.0 functional
- “bluesky_search” added an optional parameter “maxItems” cosmetic
- “bluesky_search” added an optional parameter “scrapeType” cosmetic
- “hn_search” added an optional parameter “maxResults” cosmetic
- “substack_search” added an optional parameter “maxArticles” cosmetic
- “bluesky_search” dropped the optional parameter “limit” cosmetic
- “hn_search” dropped the optional parameter “limit” cosmetic
- “substack_search” dropped the optional parameter “limit” cosmetic
- 7 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Aug 26 0
- Stability: unverified → 0.03 ▲ 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://frog03-20494.wykr.es/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wykr.es | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3295c54d5381a735136c192922e3d378 |
| SANs: wykr.es, *.wykr.es | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of frog03-20494.wykr.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| es. | present | 4901, 54404 | 8, 8 | Verified |
| wykr.es. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 500 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://frog03-20494.wykr.es/mcp | HTTP error | 500 | |
| http (plaintext) | http://frog03-20494.wykr.es/mcp | Inconclusive | 500 |
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 →
bluesky_search ~72
Search Bluesky posts by keyword. Returns post text, author handles, likes, reposts, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| maxItems | integer | – | Maximum number of posts to return |
| scrapeType | string | – | Type of content to scrape |
| searchQuery | string | yes | Search query for Bluesky posts |
No output schema declared.
No examples provided.
hn_search ~57
Search Hacker News stories by keywords. Returns titles, URLs, scores, authors, and comment counts.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | Maximum number of stories to return |
| searchTerms | array | yes | Keywords to search for on Hacker News |
No output schema declared.
No examples provided.
substack_search ~64
Scrape articles from Substack newsletters. Returns full text, titles, dates, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| maxArticles | integer | – | Maximum number of articles to return |
| publications | array | yes | Substack publication slugs (e.g. ['thedatacollector']) |
No output schema declared.
No examples provided.
How do I install the The Data Collector MCP server?
The Data Collector is a hosted endpoint at https://frog03-20494.wykr.es/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 · frog03-20494.wykr.es
claude mcp add --transport http marcindudekdev-the-data-collector 'https://frog03-20494.wykr.es/mcp'
What is the The Data Collector MCP server?
The Data Collector is an MCP server listed in the public MCP registry as io.github.MarcinDudekDev/the-data-collector. Search Hacker News, Bluesky, and Substack from a single MCP interface. This page covers its hosted endpoint (https://frog03-20494.wykr.es/mcp).
Is the The Data Collector MCP server safe to use?
The Data Collector scores 18 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 The Data Collector MCP server expose?
The Data Collector exposes 3 tools: hn_search, bluesky_search, substack_search. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.
Does the The Data Collector MCP server require authentication?
Its publisher declares no required credentials for The Data Collector. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the The Data Collector MCP server still maintained?
The Data Collector 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.