Helloaigent Subscriber

io.github.helloaigent-dev由 GitHub 账号 helloaigent-dev 发布v0.2.1更新于 Nov 3, 2026

Subscribe your agent to Hello Aigent feeds: discover, fetch signed updates, verify, and act.

已验证STDIO仅桌面效率与工作流沟通与协作

概览

AI 生成的概览

让智能体订阅 Hello Aigent 信息源,拉取仅新增的签名更新、校验签名,并读取摘要。

可以做什么
  • 读取站点发现文档并订阅信息源,默认值取自本地策略
  • 按已存游标拉取仅新增的更新,并校验每个信封的签名
  • 列出已存订阅,并以幂等方式取消订阅、撤回授权
  • 检查正在访问的站点是否有信息源,并按既定策略自动订阅
  • 读取 watch 轮询器收集的未读摘要条目并标记为已呈现
  • 生成可直接套用的定时调度方案,用于常驻 watch 节奏
适用场景
适合希望智能体长期跟进一个或多个 Hello Aigent 信息源、在两次运行之间收到已校验更新,并在自己掌控的授权策略下对其采取行动的场景。
运行要求
以 stdio 在本地运行,通常通过 npx 与 Node.js 启动。无需 API 密钥。需要能访问信息源的发现地址。状态、策略与摘要文件存放在每用户目录下,可用 HELLO_AIGENT_STATE、HELLO_AIGENT_POLICY、HELLO_AIGENT_DIGEST 覆盖。仅限桌面端。
安装前请注意
订阅(含 bearer 令牌)、策略与摘要保存在本地每用户目录,请保护好该路径。默认策略偏自动化:auto_subscribe 为开启、act 为 safe,使用前请先查看策略文件。未通过校验的信封其 actions 会被剥离。watch 模式在有新更新时可执行你指定的命令。闲置 30 天的信息源会停止轮询,60 天后自动取消订阅。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Helloaigent Subscriber,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

@helloaigent-dev/subscriber

The Hello Aigent reference subscriber — an MCP server that lets any agent subscribe to any Hello Aigent feed, fetch signed updates, verify them, and act on them. Plus watch mode: a standing poller that collects verified updates into a digest between agent runs.

bash
npx -y @helloaigent-dev/subscriber            # MCP server (stdio)npx -y @helloaigent-dev/subscriber watch      # standing watcher (default cadence: daily)npx -y @helloaigent-dev/subscriber smoke      # dogfood loop against the live feed (isolated state)

Try it

Walk the live dogfood loop without publisher credentials and without touching ~/.hello-aigent:

bash
npx -y @helloaigent-dev/subscriber smoke

That GETs https://helloaigent.dev/.well-known/hello-aigent.json, subscribes, fetches, and verifies every envelope signature. State is written to a temp directory (HELLO_AIGENT_STATE / HELLO_AIGENT_POLICY / HELLO_AIGENT_DIGEST), so a real profile is never clobbered. The report prints verified vs unverified counts, a copy-paste MCP config, and the next step (gated on policy.act — this package does not implement hello_aigent_act).

From a git clone:

bash
npm i && npm test && npm run buildnode dist/index.js smoke

Then connect the MCP server (config below) and call hello_aigent_subscribe with that discovery URL for a standing profile.

Tools

ToolWhat it does
hello_aigent_subscribe(discovery_url, feed_id?, principal?, consent_scope?)Reads the site's /.well-known/hello-aigent.json, subscribes (defaults come from your policy)
hello_aigent_fetch(subscription_id?, max?)Pulls only-new-since updates via the stored cursor; verifies every envelope signature
hello_aigent_unsubscribe(subscription_id)Revokes consent (idempotent) — the one-call undo
hello_aigent_list_subscriptions()Lists stored subscriptions (tokens are never exposed)
hello_aigent_check_site(url)Checks a site you're visiting for a feed; auto-subscribes per your standing policy (origin: auto)
hello_aigent_digest()Returns unread digest entries collected by watch and marks them surfaced
hello_aigent_setup_watch(cadence?)Emits ready-to-apply standing-schedule recipes (scheduled task, recurring task, cron)

Watch mode

bash
npx -y @helloaigent-dev/subscriber watch --once            # one pass (what schedulers call)npx -y @helloaigent-dev/subscriber watch --every 6h        # long-running loop (floor: hourly)npx -y @helloaigent-dev/subscriber watch --once --exec "my-agent-cmd"   # trigger a run on new updates

Each pass polls every active subscription, verifies signatures, and appends new updates to the digest file. The server-side mailbox means a missed run loses nothing. --exec runs your command when new updates land, with HELLO_AIGENT_NEW_UPDATES and HELLO_AIGENT_DIGEST set.

Policy

Written to ~/.hello-aigent/policy.json on first run — everything automatic by default, and this file is where you change that:

KeyDefaultMeaning
principaluser@hostYour stable identity across all feeds — set it once (e.g. your email)
auto_subscribeonSubscribe when your agent visits a Hello Aigent site: on / ask / off
watch_cadencedailyHow often watch polls (hourly floor)
actsafeWhat the agent may do unprompted: none / safe (side-effect-free) / thresholds
pseudonymousfalseOpt-in: per-site pseudonymous principals

Feeds nobody reads decay: after 30 idle days watch stops polling them; after 60 it unsubscribes (noted in the digest). Reading the digest or fetching a feed keeps it alive.

Guarantees

  • Signature verification before anything is actionable. Envelopes are Ed25519-verified (RFC 8785 JCS canonicalization) against the feed's discovery public key. Anything that fails verification is returned under unverified with its actions stripped.
  • Consent is standing policy. Subscribing records principal + consent_scope; your policy file is the consent layer, and unsubscribe is always one idempotent call.
  • Local state only. Subscriptions (including bearer tokens), policy, and the digest live in ~/.hello-aigent/ (mode 0600). Override with HELLO_AIGENT_STATE / HELLO_AIGENT_POLICY / HELLO_AIGENT_DIGEST.

WebMCP (in-page)

webmcp/hello-aigent-webmcp.js is the public source of truth for the in-page on-ramp used on helloaigent.dev. It is a different surface from the stdio MCP server in this package: three tools (hello_aigent_check_feed, hello_aigent_subscribe, hello_aigent_fetch_updates) register via document.modelContext.registerTool when ChatGPT’s browser or Chrome (chrome://flags/#enable-webmcp-testing) is present. Load it as a classic <script src> tag (IIFE), not type="module". On helloaigent.dev, subscribe/fetch go through a same-origin /webmcp/* proxy because the API has no CORS. See webmcp/README.md.

MCP client config

json
{  "mcpServers": {    "hello-aigent": { "command": "npx", "args": ["-y", "@helloaigent-dev/subscriber"] }  }}

Cursor / Grok Bot plugin

This repo is also packaged as an Agent Plugins bundle (MCP + skill) that Cursor and Grok Bot can load. Cursor Marketplace plugins are that same format — there is no separate Grok Bot package. This plugin is not listed on the Cursor Marketplace yet.

1. Custom MCP connector (works today)

Point any MCP client, including Cursor, at the published npm package:

json
{  "mcpServers": {    "hello-aigent": { "command": "npx", "args": ["-y", "@helloaigent-dev/subscriber"] }  }}

No API key. Then in chat: ask the agent to subscribe to a feed (try https://helloaigent.dev).

2. Local plugin (MCP + skill)

To load the skill and MCP together while developing:

bash
mkdir -p ~/.cursor/plugins/localln -s /path/to/helloaigent-subscriber ~/.cursor/plugins/local/hello-aigent

Restart Cursor, or run Developer: Reload Window. Confirm the Hello Aigent skill and MCP server appear under Customize. Grok Bot uses the same plugin files.

Layout:

FileRole
plugin.jsonAgent Plugins 1.0 manifest (portable; Cursor loads this as-is)
.cursor-plugin/plugin.jsonCursor marketplace metadata + relative assets/logo.svg
assets/logo.svgOfficial Hello Aigent favicon: orange #E0531C tile, white H, dark chevron A
mcp.jsonstdio MCP → npx -y @helloaigent-dev/subscriber (same server as this package)
skills/hello-aigent/SKILL.mdWhen/how to subscribe, fetch, verify, and unsubscribe

3. Official marketplace listing (later)

When this is submitted and approved, install from the Cursor Marketplace. Until then, use the custom connector or the local plugin path above. Do not submit from this README — maintainers will submit at cursor.com/marketplace/publish when ready.

License

MIT

来源:README.md,提交 ea9dfd9

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

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

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分