ProofSlip
Issue and check short-lived proof receipts so agent runs leave a verifiable audit trail without storing sensitive payloads.
Overview
ProofSlip MCP is a Ship-phase MCP server that creates, verifies, and polls ephemeral proof receipts for AI agent workflows.
What is this MCP server?
- stdio MCP via npx @proofslip/mcp-server (v0.2.3)
- Create, verify, and poll ephemeral proof receipts for agent steps
- PROOFSLIP_API_KEY required; optional PROOFSLIP_BASE_URL override
- Designed for AI agent workflows that need external proof without long-lived secrets in chat
- Registry version 0.2.3
- stdio transport via npm package @proofslip/mcp-server
- Default API base https://proofslip.ai
Community signal: 1 GitHub stars.
What problem does it solve?
Agent chains are hard to audit because chat logs mix intent with execution and lack tamper-evident proof of what actually happened.
Who is it for?
Indie builders running production-ish agent workflows who need lightweight, third-party verifiable receipts for demos, clients, or internal QA.
Skip if: Teams that only need local file logs or full enterprise SIEM with no external verification service.
What do I get? / Deliverables
After wiring ProofSlip, agents can attach verifiable receipts to critical steps so you can confirm completion without exposing long-lived secrets.
- Created proof receipts tied to agent workflow steps
- Verified or polled receipt status via MCP tools
- Configurable API base URL for staging vs production
Recommended MCP Servers
Journey fit
How it compares
Receipt-verification MCP integration, not a brainstorming or planning agent skill.
Common Questions / FAQ
Who is ai.proofslip/mcp-server for?
Solo and small-team builders shipping AI agents who want external, ephemeral proof objects for workflow steps.
When should I use ai.proofslip/mcp-server?
Use it during ship and security hardening when agent runs must be provable to collaborators, customers, or auditors.
How do I add ai.proofslip/mcp-server to my agent?
Register the npm package @proofslip/mcp-server with stdio transport, set PROOFSLIP_API_KEY, and launch via npx in your MCP client config.