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