A
licenseNot graded
qualityD
maintenanceMulti-language SAST and AI-powered fuzzing MCP server for Claude Code integration, enabling static and dynamic security analysis of code.
MIT
autotest-mcp
by MaaBlock
Related Servers
Alternatives to autotest-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceLocal MCP server for static Python/TypeScript code audits, Playwright test generation, and SDLC health checks with a 0-100 quality score.-
- AlicenseAqualityDmaintenanceDiagnose, secure, and benchmark your MCP servers. Zero-config CLI for Claude Code, Cursor, VS Code, and Windsurf.412 npm3MIT
- AlicenseCqualityBmaintenanceAn MCP server implementing Spec-Driven Development workflows for AI-agent CLIs and IDEs like Claude Code and Cursor, enabling spec-first development with automated workflow guidance and quality checks.16179 npm52MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets Claude Code and Codex delegate repository exploration and test proposals to a remote LM Studio model, while enforcing security boundaries by keeping all repository access read-only and never applying patches or running commands remotely.38 npm1MIT
- AlicenseAqualityAmaintenanceMCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.1034 npm241 PyPI135Apache 2.0
TDQS
A3.8/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a clearly distinct action and resource: generating tests, auditing code defenses, and fetching paywall status. Even though get_paywall_status is unrelated to the testing domain, there is no ambiguity between the tools.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern: generate_edge_tests, audit_code_defenses, get_paywall_status. The naming convention is uniform and predictable.
Tool Count4/5
Three tools is a reasonable count and not excessive, but the inclusion of get_paywall_status feels tangential to the autotest theme, and two core tools is a slightly small surface for a testing/auditing server.
Completeness2/5
The server can generate tests and audit code defenses, but there are no tools to run tests, retrieve generated test outputs, manage configurations, or handle results. The paywall status tool is unrelated and does not fill these workflow gaps, leaving the domain only partially covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues