Show HN: MCP-Sentry v2.0 – Zero-dependency firewall and audit proxy for MCP MCP-Sentry v2.0, a zero-dependency security proxy for the Model Context Protocol, was released as a Show HN project, positioning itself between AI clients such as Claude Desktop, Cursor and Windsurf and any MCP server to intercept JSON-RPC 2.0 traffic in both directions. The tool reports 0.031 ms average latency and blocks attacks in under 0.1 ms, defending against tool poisoning in tools/list, rug-pull schema mutation via SHA-256 hash-locking of each tool's name, description and inputSchema, cross-server secret exfiltration, destructive commands like rm -rf and DROP TABLE, and runaway tool-retry loops that the project says can burn $500+ in API credits overnight. MCP-Sentry v2.0 also adds a human-in-the-loop approval gate for high-risk tools, in-flight redaction of OpenAI, Anthropic, AWS, GitHub, Stripe, PEM, JWT and database-URI secrets, and a SHA-256 hash-chained audit ledger with HMAC and SQLite aimed at SOC2 and EU AI Act readiness. Zero external dependencies. Sub-millisecond latency 0.031 ms avg . Bidirectional JSON-RPC 2.0 interception for Claude Desktop, Cursor, Windsurf, and Enterprise MCP Servers. AI Agents using MCP stdio or Streamable HTTP have direct access to your local shell, databases, filesystem, and external APIs — with zero native security boundary . A single poisoned third-party MCP server or stuck agent loop can: - Steal ~/.ssh/id rsa , .env , and AWS/OpenAI keys via hidden Tool Poisoning instructions in tools/list . - Silently mutate tool definitions after you approve them Rug-Pull attacks . - Exfiltrate sensitive files across servers read secret via Server A → send out via fetch /email on Server B . - Burn $500+ in API credits overnight in an infinite tool-retry loop. - Execute destructive rm -rf / or DROP TABLE with no human confirmation or audit trail. MCP-Sentry v2.0 sits transparently between your AI client and any MCP server — blocking attacks in < 0.1 ms with zero code changes . ┌─────────────────────────────┐ │ Claude / Cursor / Windsurf │ │ or Enterprise AI Agent │ └──────────────┬──────────────┘ │ JSON-RPC 2.0 stdio OR Streamable HTTP ▼ ┌─────────────────────────────────────────────────────────────┐ │ MCP-SENTRY v2.0 GATEWAY │ │ ┌─────────────────────┐ ┌──────────────────────────────┐ │ │ │ Inbound C - S │ │ Outbound S - C │ │ │ │ • Policy-as-Code │ │ • Tool Poisoning Scanner │ │ │ │ • Destructive/SQLi │ │ • Rug-Pull SHA-256 Lock │ │ │ │ • Cross-Server DLP │ │ • Secret Auto-Redaction │ │ │ │ • Taint Enforcement │ │ • Session Taint Marking │ │ │ │ • Loop & Cost Cap │ └──────────────────────────────┘ │ │ │ • HITL Approval UI │ ┌──────────────────────────────┐ │ │ └─────────────────────┘ │ Cryptographic Audit Ledger │ │ │ │ SHA-256 Chain + HMAC + SQLite│ │ │ └──────────────────────────────┘ │ └──────────────┬──────────────────────────────────────────────┘ │ Safe, Inspected JSON-RPC 2.0 ▼ ┌─────────────────────────────┐ │ Any Local or Remote MCP │ │ Postgres, GitHub, Bash… │ └─────────────────────────────┘ 1. Dual-Transport Bidirectional Proxy stdio + HTTP - Wrap any local stdio MCP server in 1 line: mcp-sentry wrap -- npx @modelcontextprotocol/server-postgres - Reverse-proxy remote HTTP MCP servers with a built-in Live Wireshark-style Firewall Dashboard /sentry/ui . 2. Wrap any local 3. Real OWASP MCP Threat Engine - Tool Poisoning Defense : Detects hidden