DEV Community

Warren Koch
Warren Koch

Posted on

EXIT Protocol + MCP: Portable AI Agent History

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
Enter fullscreen mode Exit fullscreen mode

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"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

The Flow

  1. Agent connects to Platform A via MCP
  2. Agent does its work
  3. Agent calls exit_create for a signed departure marker
  4. Agent connects to Platform B
  5. Platform B calls entry_admit with the marker
  6. If it verifies and passes policy, the agent is admitted

Each marker is ~335 bytes. Signed. Verifiable offline.

Links

Top comments (0)