F
Warning
3/100
7 days ago

hermes-starter

Hermes Agent starter kit — sanitized multi-agent setup: gateway, Discord, Buzz bridge, skills, scripts, cron. Clone, fill .env, run setup.sh.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

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

pmb2

Source: github_code

Is this your MCP?

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.

// key findings
🚨
Reads files from sensitive locations
Touches: ~/AppData/Local/hermes/.env, ~/.hermes/.env
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — check_tor (line 439: result = subprocess.run()
🔐
You'll be asked for 4 credentials: DEEPSEEK_API_KEY, EMAIL_PASSWORD, LINEAR_API_KEY, POSTIZ_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDISPLAY
configHERMES_HOME
configBUZZ_RELAY_URL
configHERMES_HEALTH_MODEL
🔐 secretDEEPSEEK_API_KEY
configHERMES_MODEL_IDENTITY
configHERMES_MODEL_CONFIG
configFIREFOX_HEADLESS
configPIM_BIDI_PORT
configHERMES_HOME_BASE
configSPACEBAR_API_BASE
configSPACEBAR_WS_URL
configEMAIL_ADDRESS
🔐 secretEMAIL_PASSWORD
configHERMES_GWS_BIN
configOAUTHLIB_RELAX_TOKEN_SCOPE
configGITHUB_BASE
🔐 secretLINEAR_API_KEY
configHERMES_CITATION_LEDGER
configTG_API_ID
configTG_API_HASH
configESPLORA_BASE
🔐 secretPOSTIZ_API_KEY
configPOSTIZ_API_URL
// quality suggestions

Tool 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

47/47 tools missing one or more hints — screenshot (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); click (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); double_click (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +44 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — screenshot deletes at line 90 (Path(tmp_path).unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — check_tor (line 439: result = subprocess.run()

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

Only 1/47 tools referenced in tests (2%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: ~/AppData/Local/hermes/.env, ~/.hermes/.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Tool description accuracy

check_tor: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/pmb2-hermes-starter-wtcr8x?variant=verified)](https://m8ven.ai/mcp/pmb2-hermes-starter-wtcr8x)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 259f2ac87f0d3807222b777a1807515b9b6e3618
code hash: dd2add3ec7fd087fc6cb3281b36f4c1ddc8d9222ca9cd830f367af5d0f2a55a0
verified: 8/13/2026, 8:02:26 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client