Scopeblind Gateway MCP Server

Fail-closed Cedar policy gate + Ed25519 signed receipts for AI agent tool calls. Denies on any policy error, proves the gate is live with a startup

Remote serverstreamable-http

What is the Scopeblind Gateway MCP Server?

Fail-closed Cedar policy gate + Ed25519 signed receipts for AI agent tool calls. Denies on any policy error, proves the gate is live with a startup self-test, and

The short version

  • Fail-closed by default. — On any policy error, a missing engine, or an
  • It proves its own restraint. — serve --enforce and doctor run a startup
  • Every decision is a receipt anyone can verify. — Decisions are Ed25519-signed

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
serveStart the HTTP hook server for Claude Code (port 9377). --enforce runs the restraint self-test first; --cedar <dir> and --policy <path> select the policy.
initGenerate an Ed25519 keypair (keys/gateway.json), a config template, and a sample policy.
sampleSeed a clearly-labeled sample record (8 decisions: one blocked call, two payments; kid sample-demo) plus a tampered copy, so record, claim, verify-claim, and anchor-record are replayable from scratch before wiring an age
policySee and change the Cedar policy from the terminal: policy list (permit / forbid / default-deny per tool, with how often the gate allowed or denied it), policy show, policy allow <tool>, policy deny <tool>, policy path. A
wrapPrint a protected MCP command or patch Claude Desktop MCP servers. Dry-run by default; use --write to update Claude Desktop config.
dashboardStart a local-only dashboard on 127.0.0.1 showing tool inventory, risk, policy coverage, exact-action approvals, receipt chains, and audit export.
recommendDraft a reviewable JSON policy from observed local calls. Dry-run by default; use --write to create protect-mcp.recommended.json.
registryCreate an org identity, anchor receipt digests, and write a static verifier page. Hosted mode uploads digests only.
recordOpen a local, searchable viewer over your receipts (--live streams as the agent runs): Ed25519 signatures verified in your browser against your gateway key, capability tags, a provenance tree, and one-click signed export
claimMint a signed, position-blind attestation of a predicate over the record (--no <cap> incl. --no payment, --only <c1,c2>, --no-verdict <verdict>, --count <verdict>, --payment-under <cap>), disclosing only decision categor
anchor-recordCheckpoint the record's Merkle root + count + time range into the public log (heartbeat-friendly: skips when unchanged). A later claim whose commitment matches an anchored checkpoint is provably over the complete record
verify-claimVerify a claim pack offline: signature, recomputed Merkle root, independently recomputed predicate, and the anchor sidecar when present (binds the anchored envelope to this exact claim, then confirms the public log holds
killer-demoGenerate a complete shadow-mode to policy to approval to signed-receipt demo pack.
verify-disclosureVerify a scopeblind.selective_disclosure.v0 package and explain disclosed versus hidden fields.

How to install the Scopeblind Gateway MCP Server

{
  "mcpServers": {
    "protect-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "protect-mcp",
        "mcp"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

  • “Use Scopeblind Gateway to serve.”
  • “Use Scopeblind Gateway to init.”
  • “Use Scopeblind Gateway to sample.”

Frequently asked questions

Fail-closed Cedar policy gate + Ed25519 signed receipts for AI agent tool calls. Denies on any policy error, proves the gate is live with a startup self-test, and Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.