Agent-Blackbox MCP
Related Servers
Alternatives to Agent-Blackbox MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to work in a persistent, isolated Linux workspace with file management, Bash execution, SSH/SFTP access, and durable storage while keeping workloads contained from the host and private networks.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to checkpoint workspace state, branch parallel attempts, inspect diffs, and roll back to known-good states mid-task through MCP tools, with automatic safety checkpoints to prevent data loss.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to turn local projects into persistent workspaces, providing file editing, command execution, Git integration, and cross-session history management.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to understand, run, test, diagnose, review, benchmark, and validate real local software projects through the Model Context Protocol. It provides workspace-confined safe execution, structured evidence instead of raw logs, and Git checkpoints with guarded rollback that never destroys user work.4 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to snapshot workspace states, binary-search recorded trajectory steps, rewind to a prior good step, and retrieve per-step diffs for autonomous regression debugging. It supports self-healing debugging workflows through MCP tools.1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct action: snapshot lifecycle (list/create/rollback), reproducibility (log_command/get_recipe), and diagnostics (diagnose_failure/inspect_ports/kill_process). The only mild overlap is between diagnose_failure and inspect_ports/kill_process, since diagnosis may surface the same port/process info, but the descriptions make the intended split clear.
All eight tools use a uniform driftguard_ prefix followed by a snake_case verb_noun pattern (create_snapshot, inspect_ports, kill_process, log_command). No camelCase or stylistic deviations.
Eight tools is well within the ideal 3-15 range and each maps to a concrete operation in the blackbox/snapshot workflow. Nothing feels redundant or bolted on.
Snapshot create/list/rollback, command logging, recipe generation, and port/process diagnostics cover the core lifecycle. Minor gaps exist: no delete_snapshot or snapshot diff/compare, and no generic process listing beyond port-scoped inspection, but agents can work around these.