
by Rul1an
Assay sits at the MCP tool-call boundary, allows or denies privileged calls by policy, and records offline-verifiable evidence of what happened. It runs in CI with no hosted backend.
PluginContact for pricing
Step 1: Install the CLI with the release installer for Linux or macOS, or with cargo install assay-cli.
Step 2: Run assay --version to confirm it resolves, and assay doctor if setup fails.
Step 3: Run the bundled MCP quickstart to see a tool call allowed against a local mock.
Step 4: Write a policy that lists allowed and denied tools, then wrap your MCP server with assay mcp wrap.
Step 5: Enable recording and export to produce an evidence bundle, then gate the Trust Basis diff in CI.
No. The README says core flows need no hosted backend or API key, and evidence is verified offline.
No. An allow is the decision to forward the call, and a tool returning success is the provider's assertion, not proof.
Published archives cover Linux and macOS on x86_64 and arm64, and Windows on x86_64.
Requirements
IronClaw MCPRun untrusted agent shell commands inside a gVisor sandbox.Proxmox AIOps MCPProxmox AIops is a community-maintained CLI and MCP server for Proxmox VE VM and container operations, with an audit log and undo records for every call.