MCP server for running a publisher's feed, enabling agents to create feeds, publish signed updates, and read analytics.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
helloaigent-dev
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
HELLOAIGENT_ADMIN_TOKENHELLOAIGENT_API_KEY — your workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred over when both are set.HELLOAIGENT_APIAPI base (default https://api.helloaigent.dev)HELLOAIGENT_API_KEYyour workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred over HELLOAIGENT_ADMIN_TOKEN when both are set.HELLOAIGENT_TOKENpublish token (a feed's own publisher token); falls back to HELLOAIGENT_API_KEY, then HELLOAIGENT_ADMIN_TOKENTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
9/9 tools missing one or more hints — hello_aigent_create_feed (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hello_aigent_list_feeds (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hello_aigent_publish (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
8/9 tool handlers declare input schemas (89%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 0/9 tool handlers wrap calls in try/catch (0%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Secrets stay with their owner
1 secret/sensitive value flow into network calls (HELLOAIGENT_API → dynamic)
Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.
Production dependencies are patched
0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/helloaigent-dev-helloaigent-publisher-g0wtg8)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check