MCP.so
Sign In

drift MCP Server

@mrpkk

Basic information

Transport

streamable-http

Authentication

Check provider docs

Author

mrpkk

Submitted by

Maksim Mazunin

About drift MCP Server

Check proposed agent actions against signed mandates for amount, payee, audience, currency, time window and intent.

Connection details

https://drift.rta.lat/mcp

Setup

claude mcp add drift --transport http https://drift.rta.lat/mcp

drift MCP Server tools

3

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.

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.

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.

Overview

What is drift?

Check proposed agent actions against signed mandates for amount, payee, audience, currency, time window and intent.

How to use drift?

Add https://drift.rta.lat/mcp as a remote HTTP connection in an MCP-compatible client.

Key features

  • drift_check — Check ONE proposed action against a signed agent mandate BEFORE it happens. Returns {"verd
  • drift_session — Check a SEQUENCE of proposed actions against one mandate. Returns {submitted, allowed, den
  • drift_explain — Return the six enforcement rules in the exact order they are applied, each with a plain-la

Documentation

Repository · Website

Frequently asked questions

1

What is the drift remote MCP server?

The drift remote MCP server is a hosted Model Context Protocol endpoint at https://drift.rta.lat/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the drift MCP server?

Add the endpoint https://drift.rta.lat/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the drift MCP server require authentication?

Authentication requirements for drift have not been confirmed in this listing. Check the provider’s documentation before connecting.

4

Which transport does the drift MCP server use?

drift exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments