io.github.helloaigent-dev/helloaigent-publisher
NPM · @HELLOAIGENT-DEV/PUBLISHER · SCANNED SEP 20
Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 42 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 890 tokens (~98/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "hello_aigent_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.helloaigent-dev/helloaigent-publisher MCP server?
io.github.helloaigent-dev/helloaigent-publisher runs locally as an npm package, launched with npx -y @helloaigent-dev/publisher. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @helloaigent-dev/publisher
claude mcp add helloaigent-dev-helloaigent-publisher -- npx -y @helloaigent-dev/publisher
{
"mcpServers": {
"helloaigent-dev-helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
]
}
}
} {
"servers": {
"helloaigent-dev-helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
]
}
}
} codex mcp add helloaigent-dev-helloaigent-publisher -- npx -y @helloaigent-dev/publisher
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"helloaigent-dev-helloaigent-publisher": {
"type": "local",
"command": [
"npx",
"-y",
"@helloaigent-dev/publisher"
],
"enabled": true
}
}
} openclaw mcp add helloaigent-dev-helloaigent-publisher --command npx --arg -y --arg @helloaigent-dev/publisher
mcp_servers:
helloaigent-dev-helloaigent-publisher:
command: "npx"
args: ["-y", "@helloaigent-dev/publisher"] {
"McpServers": {
"helloaigent-dev-helloaigent-publisher": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@helloaigent-dev/publisher"
]
}
}
} assistant mcp add helloaigent-dev-helloaigent-publisher -t stdio -c npx -a -y @helloaigent-dev/publisher
{
"mcpServers": {
"helloaigent-dev-helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −4
- Stability: pass → 0.77 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@helloaigent-dev/publisher@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hello_aigent_create_feed ~176
Create a Hello Aigent feed (a stream agents subscribe to). Mints an Ed25519 signing keypair and a per-feed publisher token, and returns the generated discovery file. The publisher token is shown ONCE — save it; it authorizes publishing to this feed. Requires a workspace API key (creates the feed in that key's workspace) or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What this feed publishes |
| id | string | – | Optional feed id slug; auto-derived from the title if omitted |
| publisher_name | string | yes | The publisher/brand name |
| publisher_site | string | yes | The publisher website URL |
| title | string | yes | Human title, e.g. "Acme Roast Drops" |
| topics | array | – | Topics, e.g. ["restocks","offers"] |
No output schema declared.
No examples provided.
hello_aigent_discovery_file ~62
Get the generated discovery file (hello-aigent.json) for a feed — host it at your site's /.well-known/hello-aigent.json so agents can find and subscribe. Public; no token needed.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | Feed id |
No output schema declared.
No examples provided.
hello_aigent_event_log ~83
Filterable audit of feed events (subscribe/fetch/action/unsubscribe), newest first, agent-attributed. Requires a workspace API key (for a feed your workspace owns) or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | Feed id |
| limit | integer | – | Max rows (default 50) |
| type | string | – | Filter by event type |
No output schema declared.
No examples provided.
hello_aigent_funnel ~73
The subscribed → returned → acted cohort funnel for a feed over a window, with return-rate and act-rate. Requires a workspace API key (for a feed your workspace owns) or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | Feed id |
| window | string | – | Window (default 30d) |
No output schema declared.
No examples provided.
hello_aigent_list_feeds ~62
List the feeds you own (id, title, topics, latest_seq, discovery URL). With a workspace API key, lists only that workspace's feeds; with the admin token, lists every feed. Requires a workspace API key or the admin token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hello_aigent_overview ~71
Overview for a feed: subscribers, fetches today, 7-day return rate, signed-update count, a fetch sparkline, and recent agent-attributed activity. Requires a workspace API key (for a feed your workspace owns) or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | Feed id |
No output schema declared.
No examples provided.
hello_aigent_publish ~172
Publish a signed update to a feed. The server Ed25519-signs the envelope; subscribed agents verify it before acting. Uses the feed's own publisher token, a workspace API key (for a feed your workspace owns), or the admin token. IMPORTANT: publishing sends to every subscriber — confirm the content with the feed owner before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | Callable actions (name, endpoint, input_schema) |
| body_markdown | string | yes | Markdown body of the update |
| data | object | – | Structured data, e.g. { "sku": "ETH-YIRG" } |
| feed | string | yes | Feed id to publish to |
| summary | string | yes | One-line summary shown to agents |
| title | string | yes | – |
| type | string | yes | Update type |
No output schema declared.
No examples provided.
hello_aigent_report_event ~119
Report an action outcome for a subscription — the "acted" signal that powers the analytics funnel. Call this after a subscriber's agent completes one of your callable actions. Uses the feed's own publisher token, a workspace API key, or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| action_name | string | yes | The action that completed, e.g. "claim_offer" |
| feed | string | yes | Feed id |
| subscription_id | string | yes | The subscription that acted |
| update_id | string | – | The update the action came from, if known |
No output schema declared.
No examples provided.
hello_aigent_subscribers ~72
The feed's subscriber list — the audience you own: agent, principal, topics, consent scope, last fetch, and status (active/dormant/revoked). Requires a workspace API key (for a feed your workspace owns) or the admin token.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | Feed id |
No output schema declared.
No examples provided.
What is the io.github.helloaigent-dev/helloaigent-publisher MCP server?
io.github.helloaigent-dev/helloaigent-publisher is an MCP server listed in the public MCP registry as io.github.helloaigent-dev/helloaigent-publisher. Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics. This page covers its npm package (@helloaigent-dev/publisher).
Is the io.github.helloaigent-dev/helloaigent-publisher MCP server safe to use?
io.github.helloaigent-dev/helloaigent-publisher scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.helloaigent-dev/helloaigent-publisher MCP server expose?
io.github.helloaigent-dev/helloaigent-publisher exposes 9 tools: hello_aigent_create_feed, hello_aigent_list_feeds, hello_aigent_publish, hello_aigent_report_event, hello_aigent_overview, and 4 more. Their descriptions and schemas cost roughly 890 tokens of context every time the server is loaded.
Is the io.github.helloaigent-dev/helloaigent-publisher MCP server still maintained?
io.github.helloaigent-dev/helloaigent-publisher is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.helloaigent-dev/helloaigent-publisher MCP server under?
io.github.helloaigent-dev/helloaigent-publisher declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.