Server data from the Official MCP Registry
Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.
About
Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.
Security Report
This is a well-structured MCP server for publishing feeds and analytics with proper authentication controls. The codebase demonstrates sound security practices: credentials are loaded from environment variables (not hardcoded), API calls use Bearer token authentication with proper scoping (workspace keys scoped to owned feeds, admin tokens unrestricted), and public endpoints don't require credentials. Minor code quality issues around error handling and input validation do not materially impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: HELLOAIGENT_ADMIN_TOKEN
Environment variable: HELLOAIGENT_TOKEN
Environment variable: HELLOAIGENT_API
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-helloaigent-dev-helloaigent-publisher": {
"env": {
"HELLOAIGENT_API": "your-helloaigent-api-here",
"HELLOAIGENT_TOKEN": "your-helloaigent-token-here",
"HELLOAIGENT_ADMIN_TOKEN": "your-helloaigent-admin-token-here"
},
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
@helloaigent-dev/publisher
Hello Aigent publisher MCP — an MCP server that lets an agent run a publisher's feed: create feeds, publish signed updates, and read analytics. The producer-side counterpart to @helloaigent-dev/subscriber (which lets an agent subscribe/fetch/act).
A marketer operates their owned agent audience by telling their agent — no CLI, console, or developer.
Tools
| Tool | Auth | What it does |
|---|---|---|
hello_aigent_create_feed | workspace key or admin | Mint a feed + Ed25519 keypair + publisher token; returns the discovery file |
hello_aigent_list_feeds | workspace key or admin | List feeds you own |
hello_aigent_publish | publish token, workspace key, or admin | Build + server-sign an update; delivered to subscribers |
hello_aigent_report_event | publish token, workspace key, or admin | Report an action outcome (the "acted" analytics signal) |
hello_aigent_overview | workspace key or admin | KPI tiles, fetch sparkline, recent activity |
hello_aigent_funnel | workspace key or admin | subscribed → returned → acted funnel |
hello_aigent_event_log | workspace key or admin | Filterable, attributed audit log |
hello_aigent_subscribers | workspace key or admin | The owned-audience list (consent-aware) |
hello_aigent_discovery_file | public | Generated hello-aigent.json to host at /.well-known/ |
"workspace key" means a hak_... workspace API key — mint one from the Hello Aigent console (Settings → API keys) once you've signed up. It scopes every tool above to your own workspace: create_feed creates in your workspace, list_feeds/analytics/subscribers only ever see feeds your workspace owns, and publish/report_event only work on feeds your workspace owns. It is not admin-equivalent — it cannot create, list, or revoke API keys (that requires signing in to the console itself).
The admin token is a separate, unrestricted, ops-only credential (not something a self-serve signup ever receives) — it still works everywhere a workspace key does, for every feed, not just your own.
Configure
Set in your MCP client config (env vars):
HELLOAIGENT_API— API base (defaulthttps://api.helloaigent.dev)HELLOAIGENT_API_KEY— your workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred overHELLOAIGENT_ADMIN_TOKENwhen both are set.HELLOAIGENT_ADMIN_TOKEN— admin token; alternative toHELLOAIGENT_API_KEY(ops/dogfood use only)HELLOAIGENT_TOKEN— publish token (a feed's own publisher token); falls back toHELLOAIGENT_API_KEY, thenHELLOAIGENT_ADMIN_TOKEN
Example (Claude Desktop / any MCP client) — the common case, a self-serve workspace key:
{
"mcpServers": {
"hello-aigent-publisher": {
"command": "npx",
"args": ["-y", "@helloaigent-dev/publisher"],
"env": { "HELLOAIGENT_API_KEY": "hak_…" }
}
}
}
Then just ask your agent: "Create a feed for my coffee shop and publish a restock update," or "How many agents subscribed this week, and what's the return rate?"
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.