Skip to main content
Glama
websitebutlers

cleanroom-mcp

by websitebutlers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cleanroom-mcp

No user-submitted related servers found.

    Related Servers

    • MCPGate

      harsha-moparthy
      F
      license
      Not graded
      quality
      B
      maintenance
      A governed MCP server with OAuth 2.1 + PKCE, declarative tool scoping, row-level data filters, per-identity rate limits, and a tamper-evident audit trail.
      -

    • Proof Mode

      vikramlaishram-lang
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server implementing a multi-phase backend for structured model interactions, bounded compilation, exact-hash confirmation, and Codex-run provenance, with trust-separation hardening.
      1
      -

    • maester-mcp

      felix-e
      A
      license
      A
      quality
      C
      maintenance
      A reference MCP server that enforces identity-aware tool access using role-based permissions (Reader, Analyst, Auditor) and supports multiple identity routes like Entra RBAC, Copilot Studio, and Okta XAA. It provides read-only access to test evidence with explicit denial paths for unauthorized tools.
      7
      MIT

    • arch-optimize

      bfxh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides tools for architecture analysis, risk diagnosis, quality metrics, and regression guarding to support AI-driven code review and incremental refactoring workflows.
      5
      MIT

    • mcp-audit-server

      joepangallo
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables security auditing for MCP configurations and AI agents, including prompt injection testing, data flow tracing, and security policy generation.
      30 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but cleanroom_spec_read and cleanroom_impl_read_spec overlap in that both read specs, though the former has role-based restrictions and the latter is specifically for handed-off specs. Overall, the separation is clear enough.

    Naming Consistency4/5

    All tools share the cleanroom_ prefix and use snake_case, but the pattern varies between domain_verb (cleanroom_init, cleanroom_status) and domain_object_verb (cleanroom_spec_create, cleanroom_audit_log). This is mostly consistent but not perfectly uniform.

    Tool Count4/5

    19 tools is on the higher side but reasonable for a full clean-room workflow covering setup, team management, specs, audit, implementation, and verification. Each tool serves a distinct function in the process.

    Completeness3/5

    The core lifecycle is covered (init, spec creation/review/handoff, audit, verification), but there is no tool to edit or delete a draft spec, and no way to remove team members. These gaps could hinder workflow efficiency but are not fatal.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources