F
licenseNot graded
qualityB
maintenanceProvides MCP tools for managing disposable Docker sandboxes that let AI agents safely execute commands in isolated, ephemeral environments.
-
@reachpad/mcp
Officialby Reachpad
Related Servers
Alternatives to @reachpad/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides durable, checkpointed REPL sessions for Bun, Python, C#, and Rust, enabling agents to execute code and retrieve structured results over MCP.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with shared project memory, compact evidence-first context, status checks, durable handoffs, and encrypted cross-device checkpoints through MCP.1AGPL 3.0
- AlicenseAqualityBmaintenanceEnables local coding agents to manage disposable Colab GPU runtimes, restore and save Google Drive checkpoints, execute scripts, and safely stop VMs through MCP stdio tools.9MIT
- AlicenseBqualityCmaintenanceEnables AI agents to run shell commands, execute Python code, read and write files, search text, and create or delete folders through MCP stdio tools.9MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to operate a persistent Linux sandbox in the cloud, running commands, managing files, using Git, and publishing artifacts through a Streamable HTTP MCP endpoint.-
TDQS
A4.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool addresses a distinct concern: credit balance, environment lifecycle, and command execution are cleanly separated. Even checkpoint_environment is unambiguous because it explicitly forks an environment into a new one.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case, such as create_environment, list_environments, and delete_environment. Singular/plural usage is natural and predictable.
Tool Count5/5
Seven tools is well-scoped for managing persistent development environments: credit checking, creation, listing, inspection, command execution, forking, and deletion/archival. No tool feels redundant or out of place.
Completeness5/5
The environment lifecycle is covered end-to-end: create, read (list/get), fork/checkpoint, execute commands, and delete/archive. The credit balance tool fills the one supporting need for running environments, leaving no obvious dead ends.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive