Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hermes Prime

PYPI · HERMES-PRIME-MCP · SCANNED SEP 20

Read-only stdio MCP server for a versioned convention card in Claude Code.

Available components

54 Trust /100
Trust breakdown (7 categories)

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 setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 201 tokens (~100/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Hermes Prime MCP server?

Hermes Prime runs locally as a PyPI package, launched with uvx hermes-prime-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-prime-mcp

# add to Claude Code
claude mcp add hermes-labs-ai-hermes-prime -- uvx hermes-prime-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "hermes-labs-ai-hermes-prime": {
      "command": "uvx",
      "args": [
        "hermes-prime-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hermes-labs-ai-hermes-prime": {
      "command": "uvx",
      "args": [
        "hermes-prime-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hermes-labs-ai-hermes-prime -- uvx hermes-prime-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hermes-labs-ai-hermes-prime": {
      "type": "local",
      "command": [
        "uvx",
        "hermes-prime-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hermes-labs-ai-hermes-prime --command uvx --arg hermes-prime-mcp
# ~/.hermes/config.yaml
mcp_servers:
  hermes-labs-ai-hermes-prime:
    command: "uvx"
    args: ["hermes-prime-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hermes-labs-ai-hermes-prime": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "hermes-prime-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hermes-labs-ai-hermes-prime -t stdio -c uvx -a hermes-prime-mcp
// mcp.json
{
  "mcpServers": {
    "hermes-labs-ai-hermes-prime": {
      "command": "uvx",
      "args": [
        "hermes-prime-mcp"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 54

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Analysed pypi/hermes-prime-mcp@0.2.1a2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~137 tokens

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 →

Tool Tokens
get_conventions ~114

Return the hermes-prime CLAUDE-fragment as raw markdown — the session-priming conventions (grounding triggers, tool map, rules-most-often-forgotten). Optional scope_class returns a scoped fragment from fragments/<scope_class>.md when present; otherwise falls back to the default fragment. Call once at session start to load conventions without polluting CLAUDE.md.

NameTypeReqDescription
scope_classstringOptional scope class (e.g. 'session-init'). Falls back to the default fragment if unknown.

No output schema declared.

No examples provided.

list_scopes ~23

List available scoped fragments (one per line). Always includes 'default'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Hermes Prime MCP server?

Hermes Prime is an MCP server listed in the public MCP registry as io.github.hermes-labs-ai/hermes-prime. Read-only stdio MCP server for a versioned convention card in Claude Code. This page covers its PyPI package (hermes-prime-mcp).

Is the Hermes Prime MCP server safe to use?

Hermes Prime scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Hermes Prime MCP server expose?

Hermes Prime exposes 2 tools: get_conventions, list_scopes. Their descriptions and schemas cost roughly 137 tokens of context every time the server is loaded.

Is the Hermes Prime MCP server still maintained?

Hermes Prime is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Hermes Prime MCP server under?

Hermes Prime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.