Hermes Plant MCP Server

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 x402.

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.

Glama registry

This repo is arranged for Glama to build and inspect the MCP server without secrets or funded wallets:

• glama.json declares the GitHub maintainer.

• The root Dockerfile starts the stdio MCP server in mcp-server/.

• npm run smoke:mcp lists all local MCP tools and fetches the live x402 manifest.

• GitHub Actions validates the MCP server, Docker image, TypeScript examples, shell examples, and Python syntax.

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.

Related MCP server: Funding-mcp

Start with an assurance workflow

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.

Component catalog

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.

How an x402 call works

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             |
  |<---------------------------|--------------------------->|

1. Client makes an HTTP request.

2. Server replies with 402 Payment Required plus a PAYMENT-REQUIRED header carrying the price, network, asset, recipient, and a server-issued nonce.

3. Client parses the challenge, signs a USDC transfer authorization locally, and replays the request with a PAYMENT-SIGNATURE header.

4. Server verifies the signature via the facilitator, runs the work, settles the payment on-chain, and returns 200 OK with the result plus a PAYMENT-RESPONSE header.

The full spec lives at github.com/x402-foundation/x402.

Discovery surfaces

These let any agent or human self-onboard without help:

• hermesplant.com/llms.txt - agent-readable catalog

• hermesplant.com/openapi.json - full OpenAPI 3.1

• hermesplant.com/.well-known/x402 - x402 manifest with facilitator, network, asset, prices, and payTo metadata

• hermesplant.com/.well-known/api-catalog - RFC 9727-style API catalog

• hermesplant.com/.well-known/mcp/server-card.json - MCP server descriptor

• hermesplant.com/mcp - Streamable HTTP MCP endpoint

MCP tools in this repo

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.

Quickstart

Pick the runtime that matches your stack:

Run the MCP server locally

npm install
npm run smoke:mcp
npm start

MCP server registry build

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.

Wallet setup

Every paid-call example assumes:

• A funded wallet on Base mainnet with chain id 8453.

• A small USDC balance for paying per-call fees. Typical calls are about $0.01 to $0.50.

• An EOA private key from a standard EVM wallet such as MetaMask, Coinbase Smart Wallet, Privy, or Dynamic. Examples read it from WALLET_PRIVATE_KEY.

For testing without real funds, point your client at Base Sepolia (84532) and use the testnet x402 facilitator at https://x402.org/facilitator. Hermes Plant supports both; its /.well-known/x402 manifest declares the active network.

Status

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.

Contributing

Issues and PRs welcome. New runtime? New framework? Open a PR with one working example and a tight README.

License

MIT - see LICENSE.