Skip to main content
Glama
taewat07

STATA-MCP Repro

by taewat07

Related Servers

Alternatives to STATA-MCP Repro

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Structured workspace runtime for long-running coding agents, providing controlled workspace capabilities with task state, snapshots, checkpoints, drift detection, verification evidence, audit logs, and structured handoff.
      20
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to maintain project continuity through a file-based state hub with tasks, phases, and handoff snapshots. Provides MCP tools for reading and updating project state, with gatekeeping enforced via real-state evaluation and per-tool authorization.
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.
      -

    TDQS

    C2.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    Active tools have distinct purposes across planning, project management, run lifecycle, data inspection, and output retrieval. Deprecated tools are clearly labeled with redirecting messages, so misselection is unlikely despite some overlap in names.

    Naming Consistency3/5

    All tools use snake_case, but there is a clear split: active tools favor object_verb naming (e.g., run_prepare, data_inspect) while deprecated tools use verb_object naming (e.g., write_dofile, read_file). This mixed pattern reduces readability, though deprecated markers mitigate confusion.

    Tool Count3/5

    The total of 22 tools is heavy, and 9 of them are deprecated, artificially inflating the surface. The active 13 tools form a well-scoped set, but the obsolete entries should be removed to bring the count into an ideal range.

    Completeness4/5

    The active tool chain covers the full reproducibility lifecycle: plan preparation and approval, project initialization, run preparation/execution/monitoring, and artifact retrieval. Minor gaps like lack of list operations for runs or projects are workable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues