PEAC Protocol: Signed interaction receipts
NPM · @PEAC/MCP-SERVER
Portable signed records for agent, API, MCP, and cross-runtime interactions.
Available components
Last scanned (13 hours ago)
Scores higher than 91% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.28.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 99 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 12 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 Management70
- Stability observed for 21 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 +1
- CVE-2026-118663 affects this package: high ▼ security
- Stability: 0.97 → pass security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 +1
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 6 Nov 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7cb8ee636eac5daa9cd8af9c8813168f724aa26b82c491ee09643e6e3f87b96eda0641b0b9135d09fe250073d2ddef89d1e2011a8657e80b9b1e3adaf |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
peac_decode Decode PEAC Receipt ~50
Raw-decode a PEAC receipt JWS into header and payload objects. No signature check. Use peac_verify for trusted results.
| Name | Type | Req | Description |
|---|---|---|---|
| jws | string | yes | JWS compact serialization to decode |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | – |
| header | object | yes | – |
| payload | object | yes | – |
| verified | boolean | yes | – |
No examples provided.
peac_inspect Inspect PEAC Receipt ~67
Inspect a PEAC receipt without verifying the signature. Returns decoded header, payload metadata, and timestamps. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| full_claims | boolean | – | Include full decoded claims (may be redacted by policy) |
| jws | string | yes | JWS compact serialization to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | – |
| fullPayload | object | – | – |
| header | object | yes | – |
| payloadMeta | object | yes | – |
| redacted | boolean | yes | – |
| verified | boolean | yes | – |
No examples provided.
peac_verify Verify PEAC Receipt ~119
Verify a PEAC receipt: check Ed25519 signature, validate claims, and return structured check results. Read-only, no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Expected audience URI for binding check |
| issuer | string | – | Expected issuer URI for binding check |
| jwks | string | – | Inline JWKS JSON containing the verifying key |
| jws | string | yes | JWS compact serialization (header.payload.signature) |
| public_key_base64url | string | – | Ed25519 public key in base64url encoding (32 bytes) |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | – |
| checks | array | yes | – |
| claimsSummary | object | – | – |
| code | string | – | – |
| keySource | string | – | – |
| message | string | – | – |
| ok | boolean | yes | – |
| variant | string | – | – |
No examples provided.
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
claude mcp add peacprotocol-peac -- npx -y @peac/mcp-server
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 87 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 6 November 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 6 November 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.
What did VerifyMCP test on the PEAC Protocol: Signed interaction receipts MCP server?
VerifyMCP ran 16 checks on PEAC Protocol: Signed interaction receipts, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.