io.github.woonyong-choi/hermes-agent-mcp
PYPI · HERMES-AGENT-MCP
Operate a local Hermes Agent install over stdio: tasks, cron, config, gateway, doctor. No network.
Available components
Last scanned (2 hours ago)
Scores higher than 66% of PyPI servers
Category Workflow Automation
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 733 tokens (~45/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 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 Oct 26 +40
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −37
- Stability: 0.57 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 43 to 57. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 −15
- Malware scan: pass → unverified ▼ security
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 18 Oct 2026 · Analysed pypi/hermes-agent-mcp@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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| 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 →
config_get ~33
Read one config.yaml value by dotted key, e.g. `display.show_reasoning`.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
config_set ~117
Write one config.yaml value with an explicit type. `value_type` is one of str, int, float, bool, null, json. Passing a type avoids the YAML trap where "off", "no" and "yes" silently become booleans - several Hermes options compare against the string, so an auto-parsed value quietly does nothing. A .bak copy is written before the file changes.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| value | string | yes | – |
| value_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cron_create ~64
Create a scheduled job. `schedule` accepts what the Hermes CLI accepts, including natural language such as "every day at 23:00".
| Name | Type | Req | Description |
|---|---|---|---|
| deliver | – | – | – |
| name | string | yes | – |
| prompt | string | yes | – |
| schedule | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cron_edit ~52
Change a scheduled job in place, keeping its id and run history.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| model | – | – | – |
| prompt | – | – | – |
| reasoning_effort | – | – | – |
| schedule | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cron_list ~19
List scheduled jobs with their schedules and next run times.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cron_run ~30
Queue a job to run on the next scheduler tick instead of waiting.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cron_runs ~22
Show recorded execution attempts, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
doctor ~19
Run `hermes doctor` and return its health report.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
gateway_restart ~18
Restart the messaging gateway so configuration changes take effect.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
gateway_status ~18
Show whether the messaging gateway is running and supervised.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
hermes_ask ~71
Give the Hermes agent a task and return its reply. Runs one non-interactive turn with the agent's own tools, skills and memory. Use this for work; use the specific tools below for inspection and config.
| Name | Type | Req | Description |
|---|---|---|---|
| model | – | – | – |
| prompt | string | yes | – |
| timeout_seconds | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
hermes_status ~22
Report how this server is configured and whether the Hermes CLI answers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
model_info ~21
Show the configured default model and provider, plus Nous Portal status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sessions_list ~26
List recent sessions so you can resume or inspect one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shell ~60
Run a shell command on the Hermes host. Disabled unless HERMES_MCP_ALLOW_SHELL=1. Intended for agents that can reach this MCP server but have no terminal of their own.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| timeout_seconds | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
skills_list ~19
List installed skills with category, source and enabled state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.woonyong-choi/hermes-agent-mcp server?
io.github.woonyong-choi/hermes-agent-mcp runs locally as a PyPI package, launched with uvx hermes-agent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · hermes-agent-mcp
claude mcp add woonyong-choi-hermes-agent-mcp -- uvx hermes-agent-mcp
What is the io.github.woonyong-choi/hermes-agent-mcp server?
io.github.woonyong-choi/hermes-agent-mcp is listed in the public MCP registry as io.github.woonyong-choi/hermes-agent-mcp. Operate a local Hermes Agent install over stdio: tasks, cron, config, gateway, doctor. No network. This page covers its PyPI package (hermes-agent-mcp).
Is the io.github.woonyong-choi/hermes-agent-mcp server safe to use?
io.github.woonyong-choi/hermes-agent-mcp scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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.woonyong-choi/hermes-agent-mcp server expose?
io.github.woonyong-choi/hermes-agent-mcp exposes 16 tools: hermes_status, hermes_ask, doctor, gateway_status, gateway_restart, and 11 more. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
Is the io.github.woonyong-choi/hermes-agent-mcp server still maintained?
io.github.woonyong-choi/hermes-agent-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 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.woonyong-choi/hermes-agent-mcp server under?
io.github.woonyong-choi/hermes-agent-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.