Ext Ops Panel
Open dashboard
Comparison

signet vs PEAC Protocol: Signed interaction receipts

signet is a plugin bundle for AI coding tools published by Prismer-AI. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). PEAC Protocol: Signed interaction receipts is an MCP server published by peacprotocol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacesignetPEAC Protocol: Signed interaction receipts
Claude Code: claude-plugins-community Listed
Version: 0.4.1
Forks (GitHub): 1
Stars (GitHub): 40
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.15.0
Downloads/month (npm): 452
Downloads/week (npm): 67
Forks (GitHub): 7
Stars (GitHub): 14
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

signet vs PEAC Protocol: Signed interaction receipts
FactsignetPEAC Protocol: Signed interaction receipts
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)40 (better)14 (worse)
Forks (GitHub) (differs)1 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@peac/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0 OR MITNot stated
Repository (differs)github.com/prismer-ai/signetgithub.com/peacprotocol/peac
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

signet

In its own words, on Claude Code: claude-plugins-community:

Ed25519-signs every tool call and appends to a hash-chained, tamper-evident audit log. Zero config — signing starts immediately after install. No native dependencies (embedded WASM). Audit logs at ~/.signet/audit/ with optional CLI verification via signet audit --verify.

PEAC Protocol: Signed interaction receipts

In its own words, on Official MCP Registry:

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

How to run each

signet As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install signet@claude-community

PEAC Protocol: Signed interaction receipts As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio peac -- npx -y @peac/mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: signet · What it can do: PEAC Protocol: Signed interaction receipts · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built