MCP.Market

PEAC Protocol: Signed interaction receipts MCP server

by peacprotocol·io.github.peacprotocol/peac·v0.15.0·14 stars

Portable signed records for agent, API, MCP, and cross-runtime interactions.

A94/100grade A
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

14 stars

Reviews

Write one

Nobody has reviewed PEAC Protocol: Signed interaction receipts yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PEAC Protocol: Signed interaction receipts tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan36 source files scanned; 36 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PEAC Protocol: Signed interaction receipts compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 4,460 AI and agents servers
GitHub stars
14
more than 86% of 2,711 AI and agents servers

Install PEAC Protocol: Signed interaction receipts in Claude Code, Cursor or VS Code

Runs npx -y @peac/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add peac -- npx -y @peac/mcp-server
Add to Cursor

What the publisher says

From the PEAC Protocol: Signed interaction receipts repository's README, as published. We do not edit it. Read it on GitHub

PEAC Protocol

Portable signed records for agent, API, MCP, and cross-runtime interactions.

Automated systems call APIs, run tools, make gateway decisions, initiate commerce flows, and provision resources across organizational boundaries.

PEAC lets those systems issue portable signed interaction records so another party can verify what the issuer reported, locally, offline, or across system boundaries, without relying only on screenshots or private logs.

Record locally. Verify across boundaries.

PEAC Protocol is open-source software published and maintained by Originary, with contributions from the community.

This repository contains the official source code, releases, and developer tooling distributed under the Apache-2.0 license.

Verify a record offline

Generate the shipped sample records, then verify one locally with the generated issuer key set. The verification step does not fetch keys or call a remote verifier. pnpm dlx may download the CLI if it is not already cached.

pnpm dlx @peac/cli samples generate -o ./s
pnpm dlx @peac/cli verify ./s/valid/basic-record.jws --public-key ./s/bundles/sandbox-jwks.json

Expected:

Signature valid (offline).
  • Compare verification paths: docs/guides/verification-options.md
  • Wire PEAC into MCP, OpenTelemetry, or a gateway: docs/guides/integration-patterns.md
  • Choose a starting point by role: docs/START_HERE.md

What PEAC records

A PEAC record is a signed statement about an interaction or challenge: what the issuing system reported, not an independently established fact.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PEAC Protocol: Signed interaction receipts: common questions

Is PEAC Protocol: Signed interaction receipts MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the PEAC Protocol: Signed interaction receipts safety report
How do I install PEAC Protocol: Signed interaction receipts?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PEAC Protocol: Signed interaction receipts need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PEAC Protocol: Signed interaction receipts maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.15.0.
What can I use instead of PEAC Protocol: Signed interaction receipts?
Servers from other publishers that do the same job: Emilia Protocol MCP server, three.ws Provenance MCP server and Mockserver MCP server.
How does PEAC Protocol: Signed interaction receipts compare with other AI and agents MCP servers?
safety score 94/100 (higher than 96% of 4,460 AI and agents servers); github stars 14 (more than 86% of 2,711 AI and agents servers). Full comparison.

Alternatives to PEAC Protocol: Signed interaction receipts

Same job from other publishers: the closest match first, then the best rated.

  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    B
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • Agoragentic Agent OS MCP
    Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.
    B
  • CHAP Coordinator
    Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
    A