Openwake Recorder
Recorder is an MCP proxy. One line in the host's config puts it between Claude Code, Claude Desktop, Cursor, Windsurf or Codex and the servers they call. Every tool call becomes an event on your signed ledger: which agent, which server, which counterparty, which data classes, what outcome, how long. Arguments and results never leave the pipe.
Who, did, to, with, under, result, evidence
The agent, the tool and its action (read, write or destructive from the server's own annotations), the vendor, the data class, the policy, allowed or blocked, and a receipt. Narrow on purpose.
Enforce mode
Before forwarding, Recorder asks the Registry. A vendor that states it trains on customer data receives nothing sensitive: the host gets a tool error quoting the vendor's own words. If Openwake is unreachable the call goes through and says so. Advisory by construction.
Delegation
Every event can carry who the agent acts for, who delegated the work, the task it belongs to, the purpose and the authority it rests on, so a chain of agents is reconstructed later, not guessed.
Not tied to one protocol
MCP today. A2A, the SDK and other protocols feed the same event schema. Openwake is not an MCP security product.
{ "mcpServers": { "openwake": { "url": "https://api.openwake.ai/mcp", "headers": { "Authorization": "Bearer ow_live_…" } } } }
openwake-recorder wrap ~/.claude.json --agent acme/claude-code --key ow_live_…Openwake Recorder is one of five products on one graph: Registry, Watch, Scout, Agreements, Recorder. How they fit together.