Passage Protocol
Issue and verify cryptographically signed departure and admission records so AI agents can prove identity and boundary crossings in security-sensitive flows.
Overview
Passage Protocol is a MCP server for the Ship phase that creates Ed25519/P-256-signed departure and admission records for AI agents.
What is this MCP server?
- Departure and admission records tailored to AI agent lifecycle events
- Ed25519 and P-256 signature support for modern asymmetric verification
- NPM package @cellar-door/mcp-server with stdio MCP transport
- Version 0.1.7 protocol server for agent-boundary auditing
- Designed for provable agent handoffs rather than informal session logs
- Server version 0.1.7
- Signature algorithms: Ed25519 and P-256
- NPM identifier @cellar-door/mcp-server with stdio transport
What problem does it solve?
Multi-agent and autonomous deployments lack a standard, verifiable audit trail when agents move between environments or authorization zones.
Who is it for?
Builders designing agent gateways, compliance-sensitive automations, or custom admission control who already reason in terms of signatures and key material.
Skip if: Simple chat wrappers or CRUD SaaS apps that do not need cryptographic proof of agent boundary crossings.
What do I get? / Deliverables
After registration, your stack can mint and check signed passage records through MCP instead of relying on unsigned logs or ad-hoc tokens.
- Signed departure and admission records consumable by MCP clients
- Verifiable agent passage events using Ed25519 or P-256
- Foundation for custom admission gates in agent orchestration
Recommended MCP Servers
Journey fit
Passage Protocol belongs in Ship because it hardens how autonomous agents enter and leave trusted contexts before you expose them to users or production data. Security subphase fits signed agent passage records—this is identity and integrity control, not feature development or marketing.
How it compares
Cryptographic agent-passage MCP, not a generic OAuth login skill or ticketing integration.
Common Questions / FAQ
Who is Passage Protocol for?
Developers shipping agent systems who need signed departure and admission artifacts verifiable with Ed25519 or P-256, exposed to tools via MCP.
When should I use Passage Protocol?
Use it in Ship and security review when agents must prove they entered or left a scoped environment before production or third-party handoff.
How do I add Passage Protocol to my agent?
Install @cellar-door/mcp-server from npm, configure stdio MCP in your client, and wire your orchestrator to call passage record tools with your key management setup.