Sandbox Code Auditor MCP
Related Servers
Alternatives to Sandbox Code Auditor MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to scan code for security vulnerabilities before execution, supporting Python and JavaScript/TypeScript with deterministic AST-based analysis and optional Solana micropayments.-
- AlicenseNot gradedqualityCmaintenanceFull-stack security for AI agents — static analysis + MCP runtime interception. 31 rules detect prompt injection, data exfiltration, backdoors, tool poisoning, and cross-file attack chains. Includes MCP proxy for real-time blocking, Python AST taint tracking, multi-language injection detection (8 languages), and AI-powered deep analysis. Free, offline, zero-config.83 npm15MIT
- AlicenseBqualityCmaintenanceProvides local, dependency-free security scanning tools for LLM configurations, prompts, RAG sources, and more, enabling AI coding agents to detect prompt injections and other vulnerabilities without external network access.8MIT
- AlicenseNot gradedqualityCmaintenanceReal security scanners for AI coding agents — SAST (441 rules), secret detection (419+ patterns), dependency CVEs (OSV.dev), MCP/skill vetting, MITRE ATT&CK. Open-source, Rust, free14 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to perform static security linting for issues like dynamic eval, secret leaks, and insecure regexes, plus sub-millisecond AST symbol search across large repositories through the Model Context Protocol. It offers a zero-dependency, pure ESM runtime suited to high-concurrency agent workflows.1-
- AlicenseAqualityDmaintenanceAgent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.110 npm2MIT
TDQS
Scored across 5 tools
Each tool targets a completely distinct artifact and vulnerability class (Python AST escape, SQL taint, regex ReDoS, Seccomp BPF, CORS headers). There is no realistic scenario where an agent would confuse one for another, and the descriptions reinforce the boundaries.
All five names follow a strict snake_case pattern of <domain>_<subject>_<agent-noun>, e.g. python_ast_sandbox_escape_detector, regex_redos_exponential_scanner. The convention is applied uniformly with no stylistic deviations.
Five tools is a well-scoped set for a focused security-audit server, with each tool covering a distinct check. No tool feels redundant or missing for the stated surface.
The surface covers several sandbox-relevant classes (escape, SQLi, ReDoS, seccomp, CORS) but omits common adjacent checks like shell injection, deserialization/pickle, and path traversal. Agents can work around these gaps, and notably one tool generates filters while the rest audit, a minor asymmetry.