Warrant runs on your own machine — the client starts it, so there is no endpoint to ping. 375 installs a week from pypi. Last commit 2 Nov 2026.
Record an agent's decisions with reasons anyone can re-execute offline — verify recomputes them.
We read the source, 1 h ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
const content = fs.readFileSync(filePath, 'utf8');
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
return subprocess.run(argv, capture_output=True, text=True, timeout=timeout)
exec(compile(source, str(runtime_path), "exec"), namespace)
"canon_hex": "7b226163746f72223a7b226964223a226167656e742d784076656e646f72227d2c2262656361757365223a5b5d2c226465636973696f6e223a2270726f706f7365222c2265766964656e6365223a5b5d2c227072696f72223a5b5d2c227375626a656374223a7b2268617368223a22616161616161616161616161616161616161…
env = dict(os.environ, PYTHONPATH=str(code), PYTHONDONTWRITEBYTECODE="1")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add warrant -- uvx warrant-verify
{
"mcpServers": {
"warrant": {
"command": "uvx",
"args": [
"warrant-verify"
]
}
}
}
[mcp_servers.warrant]
command = "uvx"
args = ["warrant-verify"]
{
"mcpServers": {
"warrant": {
"command": "uvx",
"args": [
"warrant-verify"
]
}
}
}
{
"servers": {
"warrant": {
"type": "stdio",
"command": "uvx",
"args": [
"warrant-verify"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
WARRANT_STORE (Absolute path to the warrant store this server files into and verifies. Defaults to .warrants relative to the server process's working directory, which an MCP host does not guarantee), WARRANT_KEY (Ed25519 signing key. If unset, one is generated next to the store on the first filing and the result says so; any process that can read it can sign as this actor), WARRANT_ACTOR (Actor id written into filed warrants. Defaults to mcp-client@<hostname>).
Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.
Tamper-evident records of AI agent decisions. Verify offline, or publish a proof link.
A local causality ledger: records decisions and the reasons, for an agent to recall.
Records coding-agent decisions with their limits and marks old ones superseded. Local SQLite.
Verify agent actions against the system of record and get signed completion receipts.
Persistent agent memory with a decision layer: replay, restore, verify, or none — explainable.
Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
Read-only decision record: query decisions, drain decision changes, verify token.
Answers built from our own checks of this server.