The Model Context Protocol (MCP) gives AI agents a standard way to use tools. The Passage Protocol gives them a standard way to record that they used those tools and moved on.
The Gap MCP Doesn't Fill
MCP standardizes how agents discover and call tools. But it doesn't track what happens when an agent finishes with a service and moves to the next one. There's no departure record, no audit trail.
The EXIT protocol fills that gap with signed departure markers.
The MCP Server
npm install @cellar-door/mcp-server
Your MCP-compatible agent gets:
-
exit_create: create a signed departure marker -
exit_verify: verify an existing marker -
entry_admit: verify a departure record and create an admission stamp
Configuration
{
"mcpServers": {
"passage-protocol": {
"command": "npx",
"args": ["@cellar-door/mcp-server"],
"env": {
"EXIT_ORIGIN": "did:web:myplatform.example"
}
}
}
}
The Flow
- Agent connects to Platform A via MCP
- Agent does its work
- Agent calls
exit_createfor a signed departure marker - Agent connects to Platform B
- Platform B calls
entry_admitwith the marker - If it verifies and passes policy, the agent is admitted
Each marker is ~335 bytes. Signed. Verifiable offline.
Top comments (0)