Bluesky Keyword Alerts

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

Search bounded public Bluesky keywords, handles, mentions, and hashtags.

發布方自己的服務：AlertsBar

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取溝通與協作

服務詳細資訊

識別碼: io.github.telemarkdigital-publisher/bluesky-keyword-alerts
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 telemarkdigital-publisher。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.telemarkdigital-publisher%2Fbluesky-keyword-alerts.svg)](https://sourceweft.com/mcp/io.github.telemarkdigital-publisher%2Fbluesky-keyword-alerts?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

遠端 MCP 端點，執行 Apify 的 Bluesky 監控任務，依關鍵字、帳號、提及與主題標籤找出新的公開貼文，並可將符合的貼文推送到 webhook。

可以做什麼: 執行 Apify Bluesky 監控，依關鍵字、帳號、提及與主題標籤設定提醒
預設只回傳新的公開貼文，也可將符合的貼文以 POST 送到 webhook
在限定範圍內檢索公開的 Bluesky 內容
適用情境: 適合讓助理持續關注 Bluesky 上的公開討論，例如品牌帳號、產品或發布關鍵字、主題標籤與主題詞，只呈現新增的符合項目，並可轉送到 webhook 供後續自動化使用。
執行需求: 需要一個遠端 streamable HTTP 端點；未宣告任何套件、環境變數或標頭。README 說明範例不含憑證，需自行連接 Apify 與目標帳號，因此底層監控需要 Apify 帳號以及 webhook 目標。

安裝前請注意

此工具可將符合的貼文 POST 到 webhook，資料會離開目前工作階段並送到你設定的目標。執行量有上限（README 提到 Bluesky 的已儲存任務上限為 maxPostsPerRun <= 100），且 README 警告執行可能在寫入紀錄後以 FAILED、TIMED-OUT 或 ABORTED 結束，結果可能不完整。端點未宣告身分驗證。

安裝

在 SourceWeft 中

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

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

交給代理程式安裝

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

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

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

其他 MCP 客戶端

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

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

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

AI-agent index gives crawlers and coding assistants the product map, Apify links, plugin paths, and workflow boundaries.
Phase 1 visibility checkpoint lists the current public example expansion and external gates.
MCP promotion checkpoint records the live n8n, Make, MCP Registry, Smithery, Glama, and Apify agentic discovery status.
n8n creator checkpoint records the first two n8n template approvals and creator-ladder context.
AI Client Plugin Marketplaces explains the Claude/Codex plugin package layout and the safe distribution boundary.
MCP Directory Listing Pack contains per-product server.json metadata and copy for remote MCP directories.
MCP trust and uptime proof links VerifyMCP trust pages and mcpbeat uptime proof for the same product routes.

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:

Official MCP Registry: bluesky-keyword-alerts, rss-keyword-monitor, ted-tender-monitor
Glama MCP connector pages: Bluesky, RSS, TED
Smithery MCP listings: Bluesky, RSS, TED
VerifyMCP trust pages: Bluesky, RSS, TED
mcpbeat uptime proof pages: Bluesky, RSS, TED

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:

Product	Saved Task cap	Fixed retrieval limit	Reserved control rows
Bluesky	`maxPostsPerRun <= 100`	`100`	None
RSS	`maxItemsPerRun <= 200`	`200`	None
TED	`maxNewPerRun <= 999`	`1000`	Exactly 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

工具

uplifted_novice_vbl--bluesky-keyword-mention-alerts

Bluesky keyword, mention, and hashtag monitor

Run the Apify Bluesky monitor for scheduled keyword, handle, mention, and hashtag alerts. Returns only new public posts by default and can POST matching posts to a webhook.

輸入參數sortlangshandlesonlyNewhashtagskeywordsresetStatewebhookUrlexcludeTermsmaxPostsPerRun