iptables for MCP — blocks dangerous tool calls, scans for secrets, logs everything.
iptables for MCP. Blocks dangerous tool calls, scans for secret leakage, logs everything. No AI, no cloud, pure rules. Sits between your AI coding tool (Claude Code, Cursor, Windsurf) and MCP servers, intercepting every JSON-RPC message and enforcing YAML-defined policies. MCP servers have full access to your filesystem, shell, databases, and APIs. When an AI agent calls , the server executes…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
iptables for MCP. Blocks dangerous tool calls, scans for secret leakage, logs everything. No AI, no cloud, pure rules. Sits between your AI coding tool (Claude Code, Cursor, Windsurf) and MCP servers, intercepting every JSON-RPC message and enforcing YAML-defined policies. MCP servers have full access to your filesystem, shell, databases, and APIs. When an AI agent calls , the server executes whatever the agent asks — reading SSH keys, running , exfiltrating secrets. There's no built-in policy…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.