This server lets agents subscribe to Hello Aigent feeds, fetch verified updates, manage subscriptions, and collect updates into a digest.
Subscribe (hello_aigent_subscribe): Fetch a site's /.well-known/hello-aigent.json and subscribe on behalf of a principal with a defined consent scope (updates, offers, or transactional). Tokens are stored locally and never exposed.
Fetch & Verify Updates (hello_aigent_fetch): Pull new updates since the last cursor. Every envelope is Ed25519 signature-verified — verified updates are returned under updates, unverified ones under unverified with actions stripped.
Unsubscribe (hello_aigent_unsubscribe): Revoke consent for a subscription idempotently.
List Subscriptions (hello_aigent_list_subscriptions): View all stored subscriptions (active and revoked) including feed, principal, consent scope, and cursor — without exposing bearer tokens.
Check Sites & Auto-Subscribe: Check visited sites for Hello Aigent feeds and auto-subscribe based on a configurable standing policy (origin: auto).
Watch Mode: Poll active subscriptions at a configurable cadence (e.g., hourly, daily), verify signatures, and append new updates to a local digest file. Supports one-shot, long-running loop, or exec-on-update modes.
Access Digest: Retrieve unread digest entries collected by watch mode, marking them as surfaced once read.
Policy & Local State: Configure principal identity, auto-subscription behavior, watch cadence, allowed actions, and privacy settings via a local policy.json. All data is stored in ~/.hello-aigent/ with restricted permissions (0600).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@hello-aigent-subscriber fetch new updates from my subscribed feeds"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
npx @helloaigent-dev/subscriber # MCP server (stdio)
npx @helloaigent-dev/subscriber watch # standing watcher (default cadence: daily)Tool | What it does |
| Reads the site's |
| Pulls only-new-since updates via the stored cursor; verifies every envelope signature |
| Revokes consent (idempotent) — the one-call undo |
| Lists stored subscriptions (tokens are never exposed) |
| Checks a site you're visiting for a feed; auto-subscribes per your standing policy ( |
| Returns unread digest entries collected by |
| Emits ready-to-apply standing-schedule recipes (scheduled task, recurring task, cron) |
Related MCP server: Feedbagel MCP Server
npx @helloaigent-dev/subscriber watch --once # one pass (what schedulers call)
npx @helloaigent-dev/subscriber watch --every 6h # long-running loop (floor: hourly)
npx @helloaigent-dev/subscriber watch --once --exec "my-agent-cmd" # trigger a run on new updatesEach 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.
Written to ~/.hello-aigent/policy.json on first run — everything automatic by default, and this
file is where you change that:
Key | Default | Meaning |
|
| Your stable identity across all feeds — set it once (e.g. your email) |
|
| Subscribe when your agent visits a Hello Aigent site: |
|
| How often watch polls ( |
|
| What the agent may do unprompted: |
|
| Opt-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.
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.
{
"mcpServers": {
"hello-aigent": { "command": "npx", "args": ["@helloaigent-dev/subscriber"] }
}
}MIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Signed agent discovery, security attestations, paid work, and verified settlement reputation.
Issue Agent Passports and verify agent authority before value moves. Signed verification records.
Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/helloaigent-dev/helloaigent-subscriber'
If you have feedback or need assistance with the MCP directory API, please join our Discord server