An MCP server that exposes PEAC receipt operations as tools for verifying, inspecting, decoding, issuing, and bundling signed interaction receipts. It supports stdio and Streamable HTTP transports and enforces policy, size, concurrency, and security constraints.
From the registry: Signed receipts for agent, API, and MCP interactions. Portable and offline-verifiable.
Please install the `peac` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js and npm/npx** — Install Node.js so you can run the server with npx.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@peac/mcp-server"]
Note: Default transport is stdio. The server also supports HTTP via `npx @peac/mcp-server --transport http --port 3000` and binds to `127.0.0.1` by default. Read-only tools work with no extra configuration. To enable receipt issuance, start the server with `--issuer-key env:PEAC_ISSUER_KEY --issuer-id <your-issuer-id>`. Additional optional CLI flags include `--policy <path>`, `--jwks-file <path>`, `--bundle-dir <path>`, `--cors-origins <list>`, and `--trust-proxy <value>`. If using `--issuer-key env:PEAC_ISSUER_KEY`, you must define the `PEAC_ISSUER_KEY` environment variable in the client config.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Smart MCP proxy with BM25 tool discovery, quarantine security, and ~99% token savings