Scopeblind Gateway vs Platform

In-depth architectural comparison of the Scopeblind Gateway and Platform MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Scopeblind Gateway when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: INTERNAL_API_KEY.
• Primary tools included: Per-tool policy enforcement (block, rate limit, min tier), Shadow mode logs all tool calls without blocking, Enforce mode applies policies to tool calls.

Explore Scopeblind Gateway Details

Choose Platform when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: SIDCLAW_API_KEY, SIDCLAW_AGENT_ID.

Feature & Specification Comparison

Specification	Scopeblind Gateway tomjwxf Security	Platform sidclawhq Security
Summary	Security gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed receipts. Shadow mode logs every tool call; enforce mode blocks, rate-limits, or requires approval.	Governance proxy for MCP servers. Wraps any upstream server with policy evaluation, human approval workflows, and hash-chain audit trails. 18+ framework integrations. Apache 2.0 SDK.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "tomjwxf-scopeblind-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "@scopeblind/passport"
      ],
      "env": {
        "INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "sidclawhq-platform": {
      "command": "npx",
      "args": [
        "-y",
        "sidclaw-demo"
      ],
      "env": {
        "SIDCLAW_API_KEY": "YOUR_SIDCLAW_API_KEY_HERE",
        "SIDCLAW_AGENT_ID": "YOUR_SIDCLAW_AGENT_ID_HERE"
      }
    }
  }
}

Related MCP Server Comparisons