Menu

Strix MCP Proxy · Execution control for AI agents

A decision in front of your agent's tools.

Your agent can write to Notion, GitHub, Postgres and email through MCP servers. Prompts ask the model to behave and logs explain what happened afterwards. Neither decides whether the write runs, and neither gives anyone else a record they can check.

The Strix MCP Proxy is a local process between your MCP client and an MCP server. Reads you classify as low-risk pass. Writes and unclassified tools pause for a person under Guard's defaults, or follow your configuration. Every call routed through the proxy, allowed or refused, leaves a signed receipt.

Scope matters: the proxy records calls routed through it. A receipt is evidence of the proxy's recorded decision; it does not by itself prove that a downstream server executed or delivered the action.

# wrap the MCP servers your agent already uses, locally, free
npx @strixgov/guard init

# or run the proxy yourself
npm i -g @strixgov/mcp-proxy
strix-mcp-proxy --config ./proxy-config.json

What happens to a call

Classify, decide, hold or refuse, run, record.

MCP client ──▶ strix-mcp-proxy ──▶ your MCP server
                 classify → policy → (hold for a person) → run → signed receipt
CallWhat happensRecord
A read you classified as low-riskRuns.Signed receipt.
A write, or a tool nothing classifies (Guard's defaults; configurable)Waits for a person. No decision inside the timeout (default five minutes) is a refusal.Signed receipt, including the refusal.
A call your policy deniesDoes not run.Signed receipt of the refusal.

Known servers (Notion, GitHub, Slack, Linear, Postgres, filesystem, email) ship with a classification pack. A tool result that reports an error is signed as failed, not as succeeded.

Four ways in

Pick the one that fits.

Fastest start

npx @strixgov/guard init

Designed to wrap the stdio servers in Claude Code, Claude Desktop or Cursor after backing up your config, with signed approvals. End to end, only Claude Code has been observed, through Guard with unsigned approvals and with a hand-written config; signed approvals have not been exercised with a person. Guard is MIT-licensed.

Write the policy yourself

strix-mcp-proxy --config ./proxy-config.json

One server, a CI job, or a server Guard does not know. Per-tool rules, risk overrides, file or webhook approvals.

Inside your own server

@strixgov/mcp-adapter

The same governance core as a library, with no extra process.

Check a receipt

npx @strixgov/verifier chain <receipts.jsonl> --jwks <public-jwk.json>

A separate MIT package that shares no code with the proxy. Change one byte and it names the record that fails.

What has been tried

Compatibility, as observed.

Only what has actually been run is marked Observed. Everything else says so. Needs Node 20 or later for Guard (18 or later for the proxy alone) and an MCP server your client starts with a command. Real upstream servers observed: the reference filesystem server and a synthetic notes server.

Client or platformSetupTransportStatusDetail
Claude Code 2.1.330Hand-written proxy config via --mcp-configstdioObservedRead allowed; one write held then approved; one write held then refused; receipts verified offline. 2026-11-21, Linux container, Node 22, scripted approver, unsigned file approvals.
Scripted MCP client (SDK 1.29.0)Guard init, and the synthetic quickstartstdioObservedGuard init output accepted without edits; the quickstart loop runs. 2026-11-05 and 2026-11-22. A script, not a person or a product client.
Claude Code 2.1.330Guard init (unsigned approvals)stdioObservedRead allowed; one write held then approved with guard approve; one held then refused with guard deny; receipts verified offline. 2026-11-22, Linux container, Node 22, scripted approver. Signed approvals not exercised.
Claude DesktopGuard init or hand-written configstdioNot testedDesigned for; no run.
CursorGuard init or hand-written configstdioNot testedDesigned for; no run.
WindowsGuard writes a cmd /c npx entrystdioNot testedWritten by design because clients start commands without a shell; no run.
macOSAnystdioNot testedNo run.
Clean machine, cold installAnystdioNot testedEvery run so far was on a build container with the monorepo present.
A person approving at a terminalSigned approvalsstdioNot testedApprovals so far came from a script.
Hosted MCP servers (HTTPS, Streamable HTTP, SSE)AnyHTTPNot supportedA vendor's connector URL cannot be wrapped today.

What it does not do

The boundary, stated first.

  • It decides by tool name and the classification you configure. It does not read the SQL or the message body to infer intent, and it is not data-loss prevention.
  • It wraps stdio MCP servers. HTTPS-hosted MCP servers, such as a vendor's connector URL, cannot be wrapped today.
  • It covers the calls routed through it. Other credentials, other tools, and any route you did not wrap are outside it, and an operator can remove it from the config.
  • A signature shows that a key signed an unmodified record. Locally that key is generated on your machine, so it is a local assertion, not Strix-operated key custody. It does not show the policy was right or that the upstream tool did what it reported.
  • It is not capability-enforced (Mode 3). That is designed and not built.
  • It is not a certification, an attestation or a compliance claim.

Licence

Free to run. Source-available.

The proxy is under the Elastic License 2.0: free to use, including in production in front of your own agents. Guard and the verifier are MIT. This is source-available, not open source, and Strix is not on the trust path of receipt verification.

Free

Your own engineers and agents, in any environment including production. One instance per customer, on infrastructure you run, each governing only that customer's agents. Inside an on-premise product the customer operates.

Commercial licence

Offering the proxy's features to third parties as a hosted or managed service, or discussing hosted approvals, retention and enterprise features. Hosted work is person-assisted; none of it is self-serve today.

Unsure which side you are on? Email sales@strixgov.com. We will tell you which side applies. Hosted approvals are set up by a person today.

Governed Integration Pilot

One action. One boundary. A result your team checks.

We freeze one consequential action, the boundary and the approval behavior in writing, run the approved and refused scenarios in your environment, and hand you records you verify yourself with a plain list of what was and was not covered. A valid negative result is still a completed pilot. It is not a production certification.

Contact Sales for Pricing. Terms are agreed in writing before work starts.