In-depth architectural comparison of the Catalyst Governance 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
Catalyst Governance
Security · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Shield
Security · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Catalyst Governance if you need specialized Security tools running via a hosted cloud SSE transport. 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 Catalyst Governance when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Governance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger.
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
Catalyst Governance Tools (10)
catalyst_my_governance
Show your governance profile and plan capabilities
catalyst_check_action
Check if a capability is permitted before acting
catalyst_log_task
Record a task or action into the governance pipeline
catalyst_pending_approvals
List proposals awaiting human sign-off
catalyst_await_approval
Poll a specific proposal's approval status
catalyst_register_approval_webhook
Register a callback URL for approval events
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).
Catalyst Governance is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Shield belongs to Security using local stdio subprocess. Select Catalyst Governance when you need capabilities focused on security and Shield when you require tools for security.