In-depth architectural comparison of the Arai 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
Arai
Security · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Shield
Security · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Arai 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 Arai 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: ARAI_TELEMETRY_OPTOUT.
Primary tools included: Derives rules from existing instruction files (CLAUDE.md, .cursorrules, etc.), Blocks tool calls on prohibitive predicates (never, forbids, mustnot), Injects advisory context for non-blocking rules.
Policy enforcement for AI coding agents derived from existing instruction files (CLAUDE.md, .cursorrules, .windsurfrules, .github/copilot-instructions.md) — no separate YAML to maintain. Rules with prohibitive predicates (never, forbids, mustnot) emit permissionDecision: deny to block tool calls in Claude Code; advisory rules inject context. PostToolUse is correlated with PreToolUse to produce per-rule obeyed/ignored compliance verdicts in a local JSONL audit log. MCP tools — araiaddguard (register rules mid-session), arailistguards, arairecentdecisions — work in any MCP client (Claude Desktop, Cursor, Windsurf, Cline). No network on the hook hot path; opt-out anonymous telemetry.
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.
Tools & Capabilities Breakdown
Arai Tools (6)
Derives rules from existing instruction files (CLAUDE.md, .cursorrules, etc.)
Blocks tool calls on prohibitive predicates (never, forbids, mustnot)
Injects advisory context for non-blocking rules
Correlates PreToolUse and PostToolUse events for compliance verdicts
Supports native hooks for Claude Code and Grok Build
Provides MCP tools for runtime rule management and audit log access
Shield Tools (6)
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).
Arai is categorized under Security and uses a local stdio subprocess. In contrast, Shield belongs to Security using local stdio subprocess. Select Arai when you need capabilities focused on security and Shield when you require tools for security.