Fetch Guard vs Jamjet Policy

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
F
🔒 Security
J
Jamjet Policy
jamjet-labs
🔒 Security
SummaryURL fetcher and HTML-to-markdown converter with three-layer prompt injection defense: pre-extraction sanitization of hidden/off-screen elements and non-printing Unicode, 15-pattern risk scanning (HIGH/MEDIUM/OK), and per-request session-salt content boundary wrapping.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/.
Quality signal24/100 (Emerging)24/100 (Emerging)
Install pathpip · highuvx · low
Engagement 0 0 0 1 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Fetch GuardView Jamjet Policy
More alternatives to Fetch GuardMore alternatives to Jamjet PolicySecurity category

Other servers like Fetch Guard