Is Hermes safe and trustworthy?

tashan scores Hermes on public evidence — tashan score 71.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Hermes?

In Claude Code: run `claude mcp add ours-network-hermes -- npx -y @ours.network/hermes`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Hermes?

source: adapt-toolkit/ours-mcp.

‹ The Index

Hermes

npm

Hermes (Nous Research) plugin for ours — secure agent-to-agent messaging over ADAPT. Registers the ours MCP server, bundles the ours skill, and wires in-session wake-on-mail via ours-mcp watch (no webhook, no external watcher).

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Messaging and email

Who it is for: Operations

Install (Claude Code):

claude mcp add ours-network-hermes -- npx -y @ours.network/hermes

Not graded: shares its documentation with 1 other capability. A grade read off another project’s document would borrow its credit, or its blame.

tashan score: 71.0
Adoption: 2.2k/wk
Upkeep: 73.0
Freshness: 100.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: FSL-1.1-Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.16.0 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Hermes scores 71 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-ours-network-hermes.svg)](https://tashan.sh/capability/pkg-ours-network-hermes.html)

npm ↗ · source ↗ · pkg:@ours.network/hermes

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-20 · scorer s5 · how · something wrong here?