RSS Keyword Monitor

io.github.telemarkdigital-publisher由 GitHub 帳號 telemarkdigital-publisher 發布v0.2.0更新於 Oct 27, 2026

Search bounded RSS, Atom, and RDF feed matches by keyword or regex.

已驗證Streamable HTTP可網頁執行效率與工作流網頁搜尋與抓取

概覽

AI 產生的概覽

遠端 MCP 端點，執行 Apify RSS 監控任務，讓助理在 RSS、Atom 與 RDF 訂閱來源中找出新的關鍵字、正規表示式或排除規則相符項目。

可以做什麼
  • 執行 Apify RSS 監控任務，依關鍵字、正規表示式與排除規則對 RSS、Atom、RDF 訂閱來源進行排程告警。
  • 預設只回傳新相符的訂閱項目，重複執行即可看到最新命中。
  • 可選擇將相符結果以 POST 送至 webhook 目的地。
適用情境
適合讓助理持續盯住訂閱來源中的特定關鍵字、樣式或排除條件，並只回報新增相符項目，例如新聞、版本說明或安全公告的監控，而不必讀完整個訂閱來源。
執行需求
需要遠端 streamable HTTP 端點；未宣告任何套件、環境變數或標頭。README 說明底層工作流程依賴 Apify 帳號與 OAuth/MCP，匯入工作流程後須自行連接 Apify 與目的地帳號。
安裝前請注意
此工具可將相符結果 POST 至 webhook，資料會離開目前工作階段並送往你設定的目的地。README 指出執行可能在寫入資料集紀錄後以 FAILED、TIMED-OUT 或 ABORTED 結束，且不保證恰好一次投遞；取回數量受已儲存任務上限限制（maxItemsPerRun 最高 200）。範例中不含任何憑證。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 RSS Keyword Monitor，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.telemarkdigital-publisher%2Frss-keyword-monitor/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "rss-keyword-monitor": {
      "type": "http",
      "url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/rss"
    }
  }
}

README

Apify Monitoring Workflows

Public Apify Task configurations, validated n8n workflow examples, Make construction specifications, and live Make shared scenarios for monitoring Bluesky posts, RSS feeds, and TED procurement notices.

Created and maintained by Telemark Digital.

Start here

Products

  • Bluesky Keyword & Mention Alerts monitors public Bluesky posts for keywords, handles, mentions, and hashtags; its MCP route has public proof links for directories and AI agents: VerifyMCP trust and mcpbeat uptime.
  • RSS Keyword Monitor filters RSS, Atom, and RDF feeds by keyword, regular expression, and exclusion rules.
  • TED Tender Monitor is a TED tender monitor for new or changed EU procurement notices by CPV code, country, keyword, value, and notice type.

Each product directory contains public Apify Task inputs, a platform-neutral workflow contract, an n8n workflow, a Make implementation package, fixtures, and validation notes.

The TED package now includes thirteen live Apify Examples pages for high-intent procurement searches: AI procurement, cybersecurity, healthcare, SaaS/cloud software, construction, CPV 72 software, change notices and corrigenda, German managed detection, recent procurement JSON previews, EU software CPV previews, French medical equipment, Polish IT services, and renewable energy procurement.

The RSS package now includes eleven live Apify Examples pages: multi-feed keyword alerts, regex and exclusions, webhook-ready JSON, security advisories, vulnerability research, AI product news, research paper alerts, DevOps release notes, cloud platform updates, company news, and government cyber updates.

The Bluesky package now includes eleven live Apify Examples pages: keyword search, brand-handle mentions, hashtags, product launch keywords, developer tools launches, open-source maintainer discussion, AI policy posts, security keywords, data breach discussion, startup funding posts, and brand or competitor handle monitoring.

Live Make shared scenarios:

Live n8n workflow templates:

Live MCP and AI-agent directory surfaces:

AI client plugins

Foundational Codex, ChatGPT desktop, and Claude Code plugin packages are included under plugins. Each plugin exposes exactly one public Apify Actor through a product-specific Telemark MCP gateway route backed by Apify OAuth/MCP and includes a product-specific skill that keeps bounded one-off discovery separate from saved-Task monitoring.

The plugin packages passed repository-source installation plus live OAuth/MCP calls in Codex and Claude Code on 2026-07-23. These repository-source packages are separate from the official OpenAI and Anthropic review programs. See AI Client Plugin Marketplaces for the package layout, safe usage boundary, and current directory gates.

Remote MCP directory metadata for the same product routes is under mcp. Official MCP Registry, Smithery, and Glama listings are live for all three products. Smithery uses distinct free-capped product Worker URLs for cleaner tool discovery. Glama reports each connector as Healthy, VerifyMCP provides public trust pages, mcpbeat provides public uptime proof pages, and the public OAuth challenge, ownership, and server-card endpoints are live; see MCP Directory Listing Pack.

Public product icons are in assets/icons using clean external filenames. The AI-client plugin manifests omit optional icon fields for this release so the plugin packages remain text-only and easy to publish through GitHub's web editor.

Terminal-run reliability

Actor runs can commit dataset records before ending FAILED, TIMED-OUT, or ABORTED. For each terminal run they process, the public workflows fetch the run's defaultDatasetId when present, persist records under stable product-prefixed keys, and only then expose or report the terminal status. Failed empty datasets and runs without a dataset ID are reported safely. The terminal fixtures also prove replay idempotency, and the TED fixture confirms that title: null remains valid.

For Make, the construction specifications use Apify's maximum 1000-run task-runs page, one exact-key data-store cursor per Task, cursor-filtered reverse-page processing, first-run cursor priming, and an overflow stop whenever the fetched page does not contain the stored cursor run. Each publication template processes at most one selected Task run per scenario execution (maxRunsPerScenarioExecution = 1) so operation budgets stay bounded; if an account needs a longer outage window than 1000 * Apify Schedule interval, add paginated backfill before activation.

In each n8n export, dataset retrieval and Data Table upsert retry the same operation in place up to three times, waiting five seconds between attempts. These retries keep the original defaultDatasetId and stable delivery key and never rerun the Apify Task. If either operation still fails after its retries, perform manual recovery using the original run ID and its dataset; this package does not claim automatic exactly-once delivery.

Non-paginated delivery caps

The included n8n workflows and Make specifications intentionally make one non-paginated dataset request per Task run. Full retrieval therefore depends on the saved Task cap:

ProductSaved Task capFixed retrieval limitReserved control rows
BlueskymaxPostsPerRun <= 100100None
RSSmaxItemsPerRun <= 200200None
TEDmaxNewPerRun <= 9991000Exactly one appended summary row (999 + 1 = 1000)

Do not activate a workflow until the account owner has verified the matching saved Task setting. Raising a cap requires a separately designed, documented, and validated paginated workflow; it is outside this package.

Security

These examples contain no credentials. Connect your own Apify and destination accounts after importing a workflow. Read SECURITY.md before publishing or modifying an export.

Repository status

The examples are prepared and validated locally before publication. All three Make scenarios and all three n8n templates are publicly shared through the links above. The repository retains credential-free construction specifications rather than exported Make blueprint files.

See Account Gates for the GitHub publisher, n8n Creator Portal, optional n8n Cloud, and Make publication steps.

來源：README.md，提交 93066d4

工具

1

uplifted_novice_vbl--rss-keyword-monitor-only-new

RSS, Atom, and RDF keyword monitor

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.

輸入參數feedsonlyNewkeywordsresetStatewebhookUrldedupWindowmatchFieldsexcludeTermsregexPatternsincludeContentmaxItemsPerRun

版本歷史

1
  1. v0.2.0最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分