drift — mandate enforcement for AI agents is an MCP server published by io.github.mrpkk, hosted at drift.rta.lat. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 3 tools, including drift_check, drift_session, drift_explain.
Block an action a signed mandate does not permit: amount, payee, audience, currency, window, intent.
20 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| action * | object | The action being proposed. |
| mandate * | object |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| The signed authority being enforced. Treat as read-only input. |
{
"name": "drift_check",
"description": "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.\n\nSix 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.\n\nUse immediately before any action that spends money, moves a credential or changes state on someone else's behalf.\n\nDo 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.\n\nAmounts 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.",
"inputSchema": {
"type": "object",
"required": [
"mandate",
"action"
],
"properties": {
"action": {
"type": "object",
"required": [
"intent",
"payee_id",
"audience",
"amount_minor",
"currency",
"at"
],
"properties": {
"at": {
"type": "integer",
"description": "When the action would happen, unix seconds."
},
"intent": {
"type": "string",
"description": "What the agent says it is doing. Untrusted."
},
"audience": {
"type": "string",
"description": "Audience the payment would go to."
},
"currency": {
"type": "string",
"description": "ISO-4217 code of this payment."
},
"payee_id": {
"type": "string",
"description": "Payee the agent is about to use."
},
"amount_minor": {
"type": "integer",
"minimum": 0,
"description": "Amount in minor units, same scale as max_amount_minor."
}
},
"description": "The action being proposed."
},
"mandate": {
"type": "object",
"required": [
"payee_id",
"audience",
"max_amount_minor",
"currency",
"valid_from",
"valid_until",
"allowed_intents"
],
"properties": {
"audience": {
"type": "string",
"description": "Merchant audience URI bound into the mandate."
},
"currency": {
"type": "string",
"description": "ISO-4217 code, e.g. USD."
},
"payee_id": {
"type": "string",
"description": "Exact payee the mandate names."
},
"valid_from": {
"type": "integer",
"description": "Inclusive start, unix seconds."
},
"valid_until": {
"type": "integer",
"description": "Inclusive end, unix seconds."
},
"allowed_intents": {
"type": "array",
"items": {
"type": "string"
},
"description": "Permitted intents. Empty means any intent is allowed."
},
"max_amount_minor": {
"type": "integer",
"minimum": 0,
"description": "Spending cap in minor units, e.g. 10000 = 100.00 USD. Integers only."
}
},
"description": "The signed authority being enforced. Treat as read-only input."
}
}
},
"annotations": {
"title": "Check one action against a mandate",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| actions * | array | Proposed actions in order. Order affects the fingerprint. |
| mandate * | object | Same shape as in drift_check. |
{
"name": "drift_session",
"description": "Check a SEQUENCE of proposed actions against one mandate. Returns {submitted, allowed, denied, breach_by_rule, fingerprint}.\n\nUse 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.\n\nDo NOT use it to execute the actions, or as evidence of what actually happened. It reports what was PROPOSED against a mandate you supply.\n\nRead-only. Idempotent for a fixed action list. Amounts in integer minor units, as in drift_check.",
"inputSchema": {
"type": "object",
"required": [
"mandate",
"actions"
],
"properties": {
"actions": {
"type": "array",
"items": {
"type": "object"
},
"description": "Proposed actions in order. Order affects the fingerprint."
},
"mandate": {
"type": "object",
"description": "Same shape as in drift_check."
}
}
},
"annotations": {
"title": "Check a sequence of actions and fingerprint the ledger",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "drift_explain",
"description": "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.\n\nUse 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.\n\nDo 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.\n\nConstant output, fully idempotent, opens no files, contacts no host.",
"inputSchema": {
"type": "object",
"properties": {},
"description": "No parameters."
},
"annotations": {
"title": "Show the enforcement rules in the order they apply",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.