Skip to main content
Glama
csakaszamok

Purgatory (p7y)

Official
by csakaszamok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Purgatory (p7y)

No user-submitted related servers found.

    Related Servers

    • Sandbox MCP

      AbhiteshPundir
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely run commands, install dependencies, test, and modify code inside disposable, policy-enforced Docker sandboxes isolated from the host, returning results and diffs.
      15
      MIT

    • Sandbox MCP

      riyasaxena32
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute code, run tests, and build projects inside disposable Docker sandboxes, protecting the host machine through enforced isolation, filesystem snapshots, and network controls.
      15
      MIT

    • Sandbox MCP

      Dhananjay-JSR
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.
      15
      MIT

    • Advanced MCP Server

      Nom-nom-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with a secure, sandboxed environment for executing coding tasks including file operations, command execution, and testing. Features session management, policy enforcement, and Docker-based sandboxing for safe code execution and development workflows.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions, and descriptions separate overlapping areas like files vs. volumes vs. mounts and user SSH keys vs. sandbox SSH keys. The main ambiguity is among sandbox lifecycle/state operations (sleep, deep sleep, wake, keep awake, archive, restart), where subtle distinctions create some misselection risk.

    Naming Consistency4/5

    The set is predominantly consistent verb_noun snake_case, e.g. create_sandbox, list_sandbox_files, delete_ssh_key. A few names such as project_dir_link, sandbox_summary, and who_am_i break the verb_noun pattern but remain readable.

    Tool Count2/5

    37 tools is well above the typical ideal range and is heavy for a single MCP server. While the domain is broad and many tools are distinct, the large surface increases selection burden and makes the set unwieldy.

    Completeness4/5

    Coverage is broad across sandbox lifecycle, files, mounts, SSH keys, tokens, templates, runtimes, compose, and registry images. Minor-to-moderate gaps exist, such as no unarchive/restore for archived sandboxes, no template write operations, and no file move/rename, but most core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources