
Helloaigent Subscriber
io.github.helloaigent-devPublished by GitHub account helloaigent-devv0.2.1Updated Nov 3, 2026
Subscribe your agent to Hello Aigent feeds: discover, fetch signed updates, verify, and act.
Overview
Lets an agent subscribe to Hello Aigent feeds, fetch only-new signed updates, verify their signatures, and read a digest of them.
- What you can do
- Subscribe to a feed by reading a site's discovery document, with defaults taken from a local policy
- Fetch only-new updates since a stored cursor and verify every envelope signature
- List stored subscriptions and revoke consent with an idempotent unsubscribe
- Check a site for a feed and auto-subscribe according to the standing policy
- Read unread digest entries collected by the watch poller and mark them surfaced
- Emit ready-to-apply scheduling recipes for a standing watch cadence
- When to use it
- Useful when you want an agent to follow one or more Hello Aigent feeds over time, receive verified updates between runs, and act on them under a consent policy you control.
- Requirements
- Runs locally over stdio, typically via npx with Node.js. No API key is needed. Network access to the feed's discovery URL is required. State, policy and digest files live under a per-user directory, overridable with HELLO_AIGENT_STATE, HELLO_AIGENT_POLICY and HELLO_AIGENT_DIGEST. Desktop only.
Installation
In SourceWeft
- Open Helloaigent Subscriber in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
Try it
Walk the live dogfood loop without publisher credentials and without touching ~/.hello-aigent:
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:
Then connect the MCP server (config below) and call hello_aigent_subscribe with that discovery URL for a standing profile.
Tools
Watch mode
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:
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
unverifiedwith itsactionsstripped. - 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 withHELLO_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
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:
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:
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:
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
Source: README.md at commit ea9dfd9
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts