Warrant — Claude Code MCP server: features and installation
Warrant records an agent’s decisions, supporting evidence and unresolved questions. Use it to hand work to another agent with the grounds and limits intact.
MIT ★ 5 updated 2026-10-24
claude mcp add --env WARRANT_STORE=<WARRANT_STORE> --env WARRANT_KEY=<WARRANT_KEY> --env WARRANT_ACTOR=<WARRANT_ACTOR> --transport stdio mcp-server -- uvx warrant-verifyWhat Warrant does
Warrant stores duties, work transitions, evidence and questions that remain open. Each record shows what the agent established, what conditions it closed and what still needs examination. A receiving agent gets a compact account of the result rather than a full activity log.
Another agent can accept a specific closure item. The assessment can also show when its grounds have become stale or challenged; computations are checked by replay on the recipient’s side. A replayed basis is marked UNVERIFIED unless its provider is installed and accepted in the recipient’s profile.
The server works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed and Gemini CLI. The Claude Code setup command runs uvx warrant-verify. The project README also describes installing from a local checkout, with Python ≥ 3.10 and the cryptography dependency.
What it helps with
- record the basis and outcome of an agent’s work
- hand off conditions another agent still needs to accept
- separate established results from unverified claims
- surface open questions and outstanding duties
- replay a computation on the recipient’s side
Example prompts for the agent
- Record the empty-input check, including what it did not test.
- Show me the duties I still need to accept.
- Summarize this task’s result with its grounds and open questions.
How to install Warrant
Platform CLI
claude mcp add --env WARRANT_STORE=<WARRANT_STORE> --env WARRANT_KEY=<WARRANT_KEY> --env WARRANT_ACTOR=<WARRANT_ACTOR> --transport stdio mcp-server -- uvx warrant-verifyReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from warrant-verify <command>
Platform CLI
codex mcp add mcp-server --env WARRANT_STORE=<WARRANT_STORE> --env WARRANT_KEY=<WARRANT_KEY> --env WARRANT_ACTOR=<WARRANT_ACTOR> -- uvx warrant-verifyReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from warrant-verify <command>
Config file
{
"mcpServers": {
"mcp-server": {
"command": "uvx",
"args": [
"warrant-verify"
],
"env": {
"WARRANT_STORE": "<WARRANT_STORE>",
"WARRANT_KEY": "<WARRANT_KEY>",
"WARRANT_ACTOR": "<WARRANT_ACTOR>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from warrant-verify <command>
Config file
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"warrant-verify"
],
"env": {
"WARRANT_STORE": "<WARRANT_STORE>",
"WARRANT_KEY": "<WARRANT_KEY>",
"WARRANT_ACTOR": "<WARRANT_ACTOR>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from warrant-verify <command>
Platform CLI
gemini mcp add -e WARRANT_STORE=<WARRANT_STORE> -e WARRANT_KEY=<WARRANT_KEY> -e WARRANT_ACTOR=<WARRANT_ACTOR> mcp-server uvx warrant-verifyReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from warrant-verify <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Warrant
How do I install Warrant in Claude Code?
Run claude mcp add warrant -e WARRANT_KEY=<WARRANT_KEY> -- uvx warrant-verify. Replace <WARRANT_KEY> with your key.
What does Warrant do?
It records an agent’s decisions, their grounds, results and unresolved questions. Another agent can accept a specific closure and assess the result’s status.
What happens if the Sigma provider is not available to the recipient?
The recipient replays computational grounds using a provider. If that provider is not installed or its identity is not accepted in the recipient’s profile, the replayed basis is marked UNVERIFIED.