Real-time semantic security for AI coding agents and MCP tools
Real-time semantic security for AI coding agents and MCP tools in VS Code, Claude Code and Cursor. Defenter monitors every prompt, every coding agent tool call, every MCP server call, and key file and shell operations in your IDE. It acts as a semantic policy broker that understands what agents are doing, not just where they send data, so you can use AI coding agents without leaking secrets or…
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 0 source files 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”.
Real-time semantic security for AI coding agents and MCP tools in VS Code, Claude Code and Cursor. Defenter monitors every prompt, every coding agent tool call, every MCP server call, and key file and shell operations in your IDE. It acts as a semantic policy broker that understands what agents are doing, not just where they send data, so you can use AI coding agents without leaking secrets or customer data. The simplest way to use Defenter is to install the VS Code or Cursor extension: VS Code…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.