io.github.peacprotocol/peac

MCPattested
v0.15.0io.github.peacprotocolUnknownUpdated 2mo agonpmGitHub

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

Signed action records for AI agents, APIs, MCP tools, and gateways. Automated systems already call APIs, run MCP tools, make gateway decisions, report payment events, and provision resources across system boundaries. PEAC records those actions, decisions, and events as portable signed interaction records, so another party can verify what happened later without relying on screenshots, private…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2mo agoLast update
Package
Authorio.github.peacprotocol
LicenseUnknown
Version0.15.0
Sourcemcp-registry
npm@peac/mcp-server
GitHubpeacprotocol/peac
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 62a03c4
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.15.1 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Signed action records for AI agents, APIs, MCP tools, and gateways. Automated systems already call APIs, run MCP tools, make gateway decisions, report payment events, and provision resources across system boundaries. PEAC records those actions, decisions, and events as portable signed interaction records, so another party can verify what happened later without relying on screenshots, private logs, or unverifiable assertions. Record locally. Verify across boundaries. PEAC is useful when a system…

Keywords
mcp