Signed receipts for agent, API, and MCP interactions. Portable and offline-verifiable.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-peacprotocol-peac": {
"args": [
"-y",
"@peac/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Portable signed records for agent, API, MCP, and cross-runtime interactions.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@peac/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @peac/mcp-server against OSV.dev.
Click any tool to inspect its schema.
peac-termsMachine-readable PEAC terms published by a provider
/.well-known/peac.txt
peac-issuerPEAC issuer information and public keys
/.well-known/peac-issuer.json
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP Security Weekly
Get CVE alerts and security updates for io.github.peacprotocol/peac and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Portable signed records for automated interactions.
When logs are not enough, PEAC gives teams records another party can verify outside the system that produced them.
PEAC records what APIs, MCP tools, agent workflows, gateways, payment-adjacent flows, provisioning systems, runtimes, and audit systems report. It does not run those systems or make their decisions.
Record locally. Verify across boundaries.
PEAC is useful when a system does work and another party later needs to verify what happened without trusting that system's logs.
| Event | Familiar surfaces | Example record |
|---|---|---|
| API call | Stripe-style APIs, Cloudflare Workers, Vercel functions, internal HTTP services | request, response, usage, access decision, policy-visible outcome |
| MCP tool run | MCP servers, Smithery-listed tools, internal MCP servers | tool input/output reference, tool result, issuer, timestamp, signature |
| Agent action | A2A handoffs, agent-framework steps, Microsoft AGT-style runtime events | action invoked, delegated, approved, denied, cancelled, or timed out |
| Gateway decision | Cloudflare, Portkey, Kong, API gateways, AI gateways | access, routing, export, or boundary decision reported by a gateway |
| Payment event | x402, paymentauth / MPP, ACP, AP2-style commerce flows | payment request, authorization, settlement observation, mandate, dispute context |
| Provisioning event | Stripe Projects-style provider setup, Vercel deployments, GitHub Actions, Terraform-managed resources | catalog, provider link, account, credential, budget, subscription, domain, deployment, or resource lifecycle event |
These are orientation examples, not partnership claims or exclusive integration targets. PEAC records what those systems report; it does not replace them.
PEAC does not make those decisions. It records what another system reported, binds it to an issuer and time, and makes it portable for verification.
A PEAC record is signed evidence about an interaction.
| Field | Meaning |
|---|---|
| Facts | what the producing system reported happened |
| Policy or context | the terms, policy, protocol, or configuration context that applied |