mcpbeat Sign in

drift — mandate enforcement for AI agents MCP Server

answering

drift — mandate enforcement for AI agents is answering right now. Last checked 4 min ago. It exposes 3 tools. Last commit 24 Oct 2026.

Block an action a signed mandate does not permit: amount, payee, audience, currency, window, intent.

Uptime history 11 days of history · worst day 78%
11 days agonow
97.8%
Uptime 24h
89 of 91 checks
3
Tools
read from the server
789 ms
Response time
average over 24h
0
Stars
last commit 24 Oct 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

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.

Runs an external command distribution/publish.py:176
        return subprocess.run(cmd, capture_output=True, text=True,

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add drift --transport http https://drift.rta.lat/mcp
Settings → Connectors → Add custom connector, then paste this address
https://drift.rta.lat/mcp
~/.codex/config.toml
[mcp_servers.drift]
url = "https://drift.rta.lat/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "drift": {
      "url": "https://drift.rta.lat/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "drift": {
      "type": "http",
      "url": "https://drift.rta.lat/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

drift
drift_check
Check ONE proposed action against a signed agent mandate BEFORE it happens. Returns {"verdict": "ALLOW"|"DENY", "rule": <name>} plus a report with a ledger fingerprint. Six rules run in a fixed order, so a refusal names the most important reason rather than an incidental one: amount, payee, audience, currency, window, intent. Anything unclassified is DENY. Use immediately before any action that spends money, moves a credential or changes state on someone else's behalf. Do NOT use to: verify mandate signatures (AP2 does that, and this server runs after signature verification), execute the action (it only decides), or certify that an intent is truthful — "intent" arrives from the agent and is untrusted input. An agent that lies within its limits still leaves a ledger entry; proving what really happened is attest's job, not this one's. Amounts are integer minor units (cents), never floats. Window bounds are inclusive. Fully idempotent: the same inputs always give the same verdict and the mandate is never mutated.
drift_explain
Return the six enforcement rules in the exact order they are applied, each with a plain-language reason it exists. Takes no mandate and no action. Use when a refusal did not make sense, or before explaining a denial to someone whose mandate was rejected. A refusal you cannot explain is one nobody will trust. Do NOT use it to check an action — it performs no check, and cannot predict which rule will fire, only the order they are tried in. Constant output, fully idempotent, opens no files, contacts no host.
drift_session
Check a SEQUENCE of proposed actions against one mandate. Returns {submitted, allowed, denied, breach_by_rule, fingerprint}. Use for a whole plan or batch, not a single action — use drift_check for that. The fingerprint is the point: rewriting or reordering any earlier decision changes the hash, so tampering with history becomes visible instead of silent. Do NOT use it to execute the actions, or as evidence of what actually happened. It reports what was PROPOSED against a mandate you supply. Read-only. Idempotent for a fixed action list. Amounts in integer minor units, as in drift_check.

Endpoints

URLTransportStateLatencyChecked
https://drift.rta.lat/mcp streamable-http answering 861 ms 4 min ago

Alternatives to drift — mandate enforcement for AI agents

same job, measured the same way
Delego
by delego-dev

Intent-bound action authorization for AI agents: policy, human approval, and a signed audit trail.

172 installs/wk local only
Atlas MCP
by corpussanctum

Pre-action authorization for AI agents: permit, deny or escalate against a signed delegation chain.

40 installs/wk local only
Vizier
by vassiliylakhonin

Owner-signed permissions for AI agent actions; ALLOW/BLOCK/REVIEW with request-bound receipts.

1 tools answering
HANRIA agent mandate check
by hanria

Check an agent action against its operator's mandate before acting: permit, deny or escalate.

2 tools answering
Mandateguard
by ezequiellich44-cmd

Deterministic payment policy guardrail for AI agents - budgets, allowlists, signed mandates.

local only
signet-eval
by jmcentire

Deterministic policy enforcement and MCP management for AI agent tool calls.

local only
Sunaiva Gate — Agent Rule Enforcement
by sunaivacore

MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.

17 installs/wk 16 tools answering
Docimprint
by docimprint

AI document intelligence: extract, summarize, claim-check, notarize, and signed action receipts.

21 tools answering

drift — mandate enforcement for AI agents — questions

Answers built from our own checks of this server.

What can drift — mandate enforcement for AI agents do?
It exposes 3 tools, read directly from the server on our last check. Among them: drift_check, drift_explain, drift_session. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is drift — mandate enforcement for AI agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 789 ms. The bar chart above shows every period we have measured.
How do I connect drift — mandate enforcement for AI agents?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does drift — mandate enforcement for AI agents need an API key?
No. drift — mandate enforcement for AI agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is drift — mandate enforcement for AI agents?
It answers our handshake in 789 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is drift — mandate enforcement for AI agents open source?
The code is open source: it is published under the Apache-2.0 licence, written in Python and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at drift.rta.lat, which runs on its operator's own terms.