Shield vs Platform

In-depth architectural comparison of the Shield 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 Shield 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).
• Primary tools included: Pre-execution MCP call guardrails, TOFU tool-catalog pinning, Tool description and result scanning.

Explore Shield 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.
• Primary tools included: MCP governance proxy, Policy-based allow, deny, and approval decisions, Human review workflows.

Feature & Specification Comparison

Specification	Shield AperionAI Security	Platform sidclawhq Security
Summary	Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or Streamable HTTP) and blocks destructive tool calls — DROP TABLE, rm -rf, force-push — before they execute. MCP supply-chain protection: TOFU tool-catalog pinning against rug pulls, plus tool-description and tool-result scanning for tool poisoning and prompt injection. 51 starter rules, approval gates, audit logging. Single binary, Apache-2.0.	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": {
    "aperionai-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres"
      ]
    }
  }
}

{
  "mcpServers": {
    "sidclawhq-platform": {
      "command": "npx",
      "args": [
        "-y",
        "@sidclaw/sdk",
        "sidclaw-mcp-proxy",
        "stdio"
      ],
      "env": {
        "SIDCLAW_API_KEY": "YOUR_SIDCLAW_API_KEY_HERE",
        "SIDCLAW_AGENT_ID": "YOUR_SIDCLAW_AGENT_ID_HERE"
      }
    }
  }
}

Related MCP Server Comparisons