Platform vs Shield — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Platform vs Shield
In-depth architectural comparison of the Platform and Shield 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.
At a Glance & Executive Verdict
Platform
Security · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Shield
Security · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Platform if you need specialized Security tools running via a local process. Choose Shield if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
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.
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.
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.
Category & Scope
Tools & Capabilities Breakdown
Platform Tools (6)
MCP governance proxy
Policy-based allow, deny, and approval decisions
Human review workflows
Hash-chained audit trails
Stdio transport support
Agent identity and scoped permissions
Shield Tools (6)
Pre-execution MCP call guardrails
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).
Platform is categorized under Security and uses a local stdio subprocess. In contrast, Shield belongs to Security using local stdio subprocess. Select Platform when you need capabilities focused on security and Shield when you require tools for security.