mcp-testbed
Related Servers
Alternatives to mcp-testbed
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides structured, sandboxed test and lint feedback for coding agents, returning compact typed verdicts with failure fingerprints instead of raw runner output. It enables impact-selected test execution in isolated containers, distinguishing pre-existing failures from regressions.417 PyPIApache 2.0
- AlicenseAqualityDmaintenanceEnables running code against tests in an isolated sandbox to obtain PASS/FAIL verdicts with signed, offline-checkable certificates, and generating verified code with attached certificates after execution against derived tests.238 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants and coding tools to run code in 46 languages and judge it against test cases or stored problems in isolated sandboxes.453 PyPIMIT
- AlicenseBqualityBmaintenanceEnables coding agents to run isolated sandbox verification workflows: capture base and candidate workspaces, reproduce runtime regressions, compare results, repair code, rerun suites, and export replayable evidence.10MIT
- AlicenseAqualityCmaintenanceEnables coding agents to compile supplied files, run optional focused tests, and get static findings across ten programming languages, providing a deterministic feedback loop on the code they are about to return.1MIT
- AlicenseAqualityDmaintenanceProvides secure access to containerized build environments for software projects, enabling AI assistants to execute builds, run tests, manage git operations, and inspect build artifacts without requiring local installation of dependencies.6MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: create workspace, read/list files, write files, run tests, and destroy workspace. There is no overlap in purpose, so an agent can easily select the right tool.
All tool names follow a consistent verb_noun pattern (create_workspace, read_workspace, write_files, run_tests, destroy_workspace), using snake_case throughout. The naming is predictable and intuitive.
Five tools is appropriate for the scope of managing isolated test workspaces and running tests. Each tool serves a necessary function without redundancy or bloat.
The set covers the full lifecycle of a test workspace: creation, reading, writing, test execution, and destruction. No essential operations are missing; write_files handles overwrites, and read_workspace supports both listing and file content retrieval.