MCP Tool Run Records

MCP server (5 built-in tools)

Install the PEAC MCP server for Claude Desktop, Cursor, VS Code, or any MCP client. It exposes five tools for record operations.

npm install -g @peac/mcp-server

• peac_verify Verify a record offline given a JWS and public key
• peac_inspect Decode and inspect a record's claims
• peac_decode Decode without signature verification
• peac_issue Issue a new signed record (requires a signing key)
• peac_create_bundle Bundle multiple records into a portable archive

Carry records in tool responses

Use @peac/mappings-mcp to attach a record to an MCP tool response through _meta. The carrier embeds org.peacprotocol/receipt_ref and org.peacprotocol/receipt_jws, with an 8 KB embed limit.

import { attachReceiptToMeta, computeReceiptRef } from '@peac/mappings-mcp';
import { issue } from '@peac/protocol';

const record = await issue({ iss, sub, typ: 'access' }, privateKey);
const meta = await attachReceiptToMeta({}, record, computeReceiptRef(record));

return {
  content: [{ type: 'text', text: result }],
  _meta: meta,
};

Verify on the consuming side

A client reading the tool response extracts the record from _meta with extractReceiptFromMetaAsync, then verifies it offline with the issuer's public key. The receipt_ref is checked as sha256(receipt_jws) at extraction.

import { extractReceiptFromMetaAsync } from '@peac/mappings-mcp';
import { verifyLocal } from '@peac/protocol';

const jws = await extractReceiptFromMetaAsync(response._meta);
if (jws) {
  const result = await verifyLocal(jws, publicKey);
  // result.valid, result.claims.iss, result.claims.type
}

Semantic Boundary

Links