MCP server: mandates as a tool for agents
Through the Model Context Protocol an agent uses mandates directly as a tool: issue a sandbox mandate, check an action, see open escalations. Two servers are available — a local one with five tools and a hosted one that only reads and verifies.
Local server (stdio)
mcp/server.mjs offers mandact_sandbox_issue, mandact_verify, mandact_revoke, mandact_list_escalations and mandact_decide_escalation. The complete lifecycle is verified over stdio — for development and your own operating environments.
Hosted server: deliberately powerless
The hosted MCP access knows only verify_agent_mandate. An agent can neither revoke nor approve an escalation through it — otherwise it could grant itself the human approval.
Why it matters
Agent frameworks increasingly speak MCP. A mandate tool in the same protocol means the agent asks before acting, instead of every integration inventing its own check.
Status
Local server in the repository (mcp/server.mjs); hosted verify server (mcp/verify-server.mjs) read-only.