In-depth architectural comparison of the Jamjet Policy and Scopeblind Gateway 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
Jamjet Policy
Security · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Scopeblind Gateway
Security · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Jamjet Policy if you need specialized Security tools running via a local process. Choose Scopeblind Gateway 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 Jamjet Policy 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).
MCP stdio interceptor (@jamjet/mcp-shim) that applies one YAML policy file (block / requireapproval / audit / budget cap) to tools/call requests before they reach the real MCP server. The same policy also runs in Claude Code PreToolUse hooks (@jamjet/claude-code-hook), OpenAI Agents SDK guardrails (@jamjet/openai-guardrail), and JamJet's Python/TS SDKs — jamjet audit show tails every decision across every adapter from /.jamjet/audit/.
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.
Category & Scope
Tools & Capabilities Breakdown
Jamjet Policy Tools (6)
MCP stdio interception
YAML policy enforcement
Block rules
Approval requirements
Audit logging
Budget caps
Scopeblind Gateway Tools (6)
Per-tool policy enforcement (block, rate limit, min tier)
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).
Jamjet Policy is categorized under Security and uses a local stdio subprocess. In contrast, Scopeblind Gateway belongs to Security using local stdio subprocess. Select Jamjet Policy when you need capabilities focused on security and Scopeblind Gateway when you require tools for security.