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.

PEAC Protocol: Signed interaction receipts

NPM · @PEAC/MCP-SERVER · SCANNED SEP 20

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

Available components

npm · @peac/mcp-server 95
0 this week 95 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to peacprotocol/peac). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 41 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 236 tokens (~78/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the PEAC Protocol: Signed interaction receipts MCP server?

PEAC Protocol: Signed interaction receipts runs locally as an npm package, launched with npx -y @peac/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @peac/mcp-server

# add to Claude Code
claude mcp add peacprotocol-peac -- npx -y @peac/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "peacprotocol-peac": {
      "command": "npx",
      "args": [
        "-y",
        "@peac/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "peacprotocol-peac": {
      "command": "npx",
      "args": [
        "-y",
        "@peac/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add peacprotocol-peac -- npx -y @peac/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "peacprotocol-peac": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@peac/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add peacprotocol-peac --command npx --arg -y --arg @peac/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  peacprotocol-peac:
    command: "npx"
    args: ["-y", "@peac/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "peacprotocol-peac": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@peac/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add peacprotocol-peac -t stdio -c npx -a -y @peac/mcp-server
// mcp.json
{
  "mcpServers": {
    "peacprotocol-peac": {
      "command": "npx",
      "args": [
        "-y",
        "@peac/mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
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 npm/@peac/mcp-server@0.15.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo peacprotocol/peac
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/peacprotocol/peac/.github/workflows/publish.yml@refs/tags/v0.15.0
Rekor log index 1689125947
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:7cb8ee636eac5daa9cd8af9c8813168f724aa26b82c491ee09643e6e3f87b96eda0641b0b9135d09fe250073d2ddef89d1e2011a8657e80b9b1e3adaf

Background: How many MCP packages publish verified provenance →

Dependencies 102 packages
Packages resolved 102
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~236 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
peac_decode ~50

Raw-decode a PEAC receipt JWS into header and payload objects. No signature check. Use peac_verify for trusted results.

NameTypeReqDescription
jwsstringyesJWS compact serialization to decode
NameTypeReqDescription
_metaobjectyes–
headerobjectyes–
payloadobjectyes–
verifiedbooleanyes–

No examples provided.

peac_inspect ~67

Inspect a PEAC receipt without verifying the signature. Returns decoded header, payload metadata, and timestamps. Read-only.

NameTypeReqDescription
full_claimsboolean–Include full decoded claims (may be redacted by policy)
jwsstringyesJWS compact serialization to inspect
NameTypeReqDescription
_metaobjectyes–
fullPayloadobject––
headerobjectyes–
payloadMetaobjectyes–
redactedbooleanyes–
verifiedbooleanyes–

No examples provided.

peac_verify ~119

Verify a PEAC receipt: check Ed25519 signature, validate claims, and return structured check results. Read-only, no side effects.

NameTypeReqDescription
audiencestring–Expected audience URI for binding check
issuerstring–Expected issuer URI for binding check
jwksstring–Inline JWKS JSON containing the verifying key
jwsstringyesJWS compact serialization (header.payload.signature)
public_key_base64urlstring–Ed25519 public key in base64url encoding (32 bytes)
NameTypeReqDescription
_metaobjectyes–
checksarrayyes–
claimsSummaryobject––
codestring––
keySourcestring––
messagestring––
okbooleanyes–
variantstring––

No examples provided.

Common questions

What is the PEAC Protocol: Signed interaction receipts MCP server?

PEAC Protocol: Signed interaction receipts is an MCP server listed in the public MCP registry as io.github.peacprotocol/peac. Portable signed records for agent, API, MCP, and cross-runtime interactions. This page covers its npm package (@peac/mcp-server).

Is the PEAC Protocol: Signed interaction receipts MCP server safe to use?

PEAC Protocol: Signed interaction receipts scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 PEAC Protocol: Signed interaction receipts MCP server expose?

PEAC Protocol: Signed interaction receipts exposes 3 tools: peac_verify, peac_inspect, peac_decode. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.

Is the PEAC Protocol: Signed interaction receipts MCP server still maintained?

PEAC Protocol: Signed interaction receipts 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 PEAC Protocol: Signed interaction receipts MCP server under?

PEAC Protocol: Signed interaction receipts declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.