RSS Keyword Monitor
REMOTE · TELEMARK-APIFY-MONITORING-MCP.KATFU111111.WORKERS.DEV · SCANNED OCT 12
Search bounded RSS, Atom, and RDF feed matches by keyword or regex.
Available components
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 Security81
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1200 tokens (~1200/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RSS Keyword Monitor MCP server?
RSS Keyword Monitor is a hosted endpoint at https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss, 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 · telemark-apify-monitoring-mcp.katfu111111.workers.dev
claude mcp add --transport http telemarkdigital-publisher-rss-keyword-monitor 'https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss'
{
"mcpServers": {
"telemarkdigital-publisher-rss-keyword-monitor": {
"url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
}
}
} {
"servers": {
"telemarkdigital-publisher-rss-keyword-monitor": {
"type": "http",
"url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
}
}
} [mcp_servers.telemarkdigital-publisher-rss-keyword-monitor] url = "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"telemarkdigital-publisher-rss-keyword-monitor": {
"type": "remote",
"url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss",
"enabled": true
}
}
} openclaw mcp add telemarkdigital-publisher-rss-keyword-monitor --url 'https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss' --transport streamable-http
mcp_servers:
telemarkdigital-publisher-rss-keyword-monitor:
url: "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss" {
"McpServers": {
"telemarkdigital-publisher-rss-keyword-monitor": {
"Transport": "http",
"Url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
}
}
} assistant mcp add telemarkdigital-publisher-rss-keyword-monitor -t streamable-http -u 'https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss'
{
"mcpServers": {
"telemarkdigital-publisher-rss-keyword-monitor": {
"type": "http",
"url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 10 Oct 26 0
- Server version: 0.17.3 → 0.17.4 functional
- 1 Oct 26 0
- Server version: 0.16.0 → 0.17.1 functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1016 → 1200 ▼ functional
- Server version: 0.15.7 → 0.16.0 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 12 Oct 2026 · Probed https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=katfu111111.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e651008675cd5e6b94d73eb8f66988096b |
| SANs: *.katfu111111.workers.dev, katfu111111.workers.dev | ||||||
| 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 telemark-apify-monitoring-mcp.katfu111111.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations", resource_metadata="https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/rss"
Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations", resource_metadata="https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/rss"| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/rss |
|---|---|
| Retrieved | Yes |
| Resource | https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss |
| Authorisation server | https://console-backend.apify.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss | Verified | 200 | |
| http (plaintext) | http://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss | Inconclusive | 401 |
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 →
uplifted_novice_vbl--rss-keyword-monitor-only-new RSS, Atom, and RDF keyword monitor ~283
Run the Apify RSS monitor for scheduled keyword, regex, and exclusion alerts across RSS, Atom, and RDF feeds. Returns only new matching feed items by default and can POST to a webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| dedupWindow | integer | – | Days an item remains in the seen-set before it can be delivered again. |
| excludeTerms | array | – | Case-insensitive terms that remove matched items before delivery and billing. |
| feeds | array | – | RSS, Atom, or RDF feed URLs to monitor. |
| includeContent | boolean | – | Include full content:encoded HTML from the feed when present. |
| keywords | array | – | Case-insensitive keywords or phrases. Empty returns every new item. |
| matchFields | array | – | Feed item fields to search: title, description, content, and categories. |
| maxItemsPerRun | integer | – | Maximum feed items delivered and charged in one run. |
| onlyNew | boolean | – | When true, return only items not previously delivered by this saved Task. |
| regexPatterns | array | – | Case-insensitive regular expressions, OR-matched with keywords. |
| resetState | boolean | – | Reset the saved seen-set and HTTP validators once, then turn it off. |
| webhookUrl | string | – | Optional webhook endpoint that receives a summary and up to 50 newest matched items. |
No output schema declared.
No examples provided.
What is the RSS Keyword Monitor MCP server?
RSS Keyword Monitor is an MCP server listed in the public MCP registry as io.github.telemarkdigital-publisher/rss-keyword-monitor. Search bounded RSS, Atom, and RDF feed matches by keyword or regex. This page covers its hosted endpoint (https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss).
Is the RSS Keyword Monitor MCP server safe to use?
RSS Keyword Monitor scores 85 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 RSS Keyword Monitor MCP server expose?
RSS Keyword Monitor exposes 1 tool: uplifted_novice_vbl--rss-keyword-monitor-only-new. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.
Does the RSS Keyword Monitor MCP server require authentication?
Yes. RSS Keyword Monitor asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RSS Keyword Monitor MCP server still maintained?
RSS Keyword Monitor is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.