Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.hermesplant.com/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.jessegdotio-hermes-plant https://mcp.hermesplant.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.jessegdotio-hermes-plant": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.hermesplant.com/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
Runnable MCP server and integration examples for Hermes Plant, the Agent Commerce Assurance layer that lets AI agents preflight, approve, and prove consequential actions. Start with a one-cent action-safety check, route only high-risk actions into signed review evidence, and pay per call over .
Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools.
What's here: a runnable stdio MCP bridge for registry crawlers and local clients, plus drop-in examples in curl, TypeScript, Python, CrewAI, LangChain, and MCP client configs for Claude Desktop / Cline / Cursor.
Install the public, fail-closed Action Safety skill for Codex, Claude Code, Cursor, and other Agent Skills-compatible clients:
npx [email protected] add JesseGdotIO/hermesplant-mcp-server --skill protect-agent-action
The skill calls the one-cent quick gate before an exact consequential action, binds the result to that unchanged action, and escalates high or critical risk only when the additional $0.25 is authorized. Review triage is never treated as human approval and the skill never expands the caller's permissions.
For the complete production tool surface, use the canonical Hermes Plant — Agent Commerce Assurance connector on Glama. It exposes Action Safety, Spend Assurance, signed evidence, payment-policy checks, and the component x402 tools through the live Streamable HTTP endpoint.
This repository is the portable, no-secret discovery bridge. It lets registry crawlers and local clients inspect the live catalog and payment contracts without signing a wallet message or spending funds. The hosted connector is the buyer-facing path for invoking the production tools.
This repo is arranged for Glama to build and inspect the MCP server without secrets or funded wallets:
glama.json declares the GitHub maintainer.Dockerfile starts the stdio MCP server in mcp-server/.npm run smoke:mcp lists all local MCP tools and fetches the live x402 manifest.A Glama release is still an account-side action, not a GitHub release. After claiming the server in Glama, use the Dockerfile admin page to deploy the build, wait for the build test to pass, then publish a Glama release version. That release unlocks Glama's Server Coherence and Tool Definition Quality scoring.
Hermes Plant governs consequential actions and payments; these independent servers cover adjacent layers of an agent stack:
These links describe functional complementarity, not partnerships or endorsements.
Use the free API key for up to 250 calls/month, the $29/month Agent API Pass for regular volume, or per-call USDC on Base. Public proof and machine-readable contracts are available at hermesplant.com/proof and hermesplant.com/openapi.json.
Nineteen hosted x402 endpoints remain available as composable utilities:
Agents discover endpoints through OpenAPI, llms.txt, the x402 manifest, the API catalog, MCP metadata, or agent skills. The workflow links above carry source-specific attribution so registry traffic can be evaluated against paid calls instead of impressions.
Client Hermes Plant Facilitator
| | |
| POST /endpoint | |
|--------------------------->| |
| 402 Payment Required | |
| + PAYMENT-REQUIRED | |
|<---------------------------| |
| sign payment locally | |
| POST /endpoint | |
| + PAYMENT-SIGNATURE | |
|--------------------------->| verify signature |
| |--------------------------->|
| | ok |
| |<---------------------------|
| 200 OK + result | settle payment |
|<---------------------------|--------------------------->|
402 Payment Required plus a PAYMENT-REQUIRED header carrying the price, network, asset, recipient, and timeout.PAYMENT-SIGNATURE header.200 OK with the result plus a PAYMENT-RESPONSE header.The full spec lives at github.com/x402-foundation/x402.
These let any agent or human self-onboard without help:
The runnable stdio server exposes five read-only discovery tools:
These local tools do not sign wallet messages, approve transactions, call paid endpoints, or spend USDC. They expose the discovery layer that clients need before invoking paid hosted tools.
Pick the runtime that matches your stack:
npm install
npm run smoke:mcp
npm start
This repo includes a root glama.json and root Dockerfile for MCP registry crawlers:
docker build -t hermesplant-mcp-server .
docker run --rm -i hermesplant-mcp-server
The container starts the stdio MCP bridge in mcp-server/, which exposes Hermes Plant discovery tools and hosted MCP metadata without requiring API keys.
The guarded paid-call examples require:
8453.EVM_PRIVATE_KEY plus the explicit opt-in HERMES_ALLOW_PAYMENT=1.The included CashflowLens clients cap payment requirements at $0.20 USDC and register only Base mainnet. Leave the opt-in unset for imports and tests. Never commit a private key. These production examples do not claim testnet support; use an x402 test resource server for testnet integration work.
These examples target the production deployment at hermesplant.com. Endpoint signatures may evolve, so cross-reference openapi.json and the /.well-known/x402 manifest before going to production.
Issues and PRs welcome. New runtime? New framework? Open a PR with one working example and a tight README.
MIT - see LICENSE.
© 2026 MCP Directory.
Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools.
{ "mcpServers": { "io.github.jessegdotio-hermes-plant": { "url": "https://mcp.hermesplant.com/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Hermes Plant — Agent Commerce Assurance is reached over HTTP.
Last checked 2026-11-09. Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools.