Skip to main content
Glama
huytrao
by huytrao

Related Servers

Alternatives to hugomemo-qa

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables bounded, deterministic triage verdicts for server health, fleet status, and timeline investigation through a simulated execution-boundary MCP server.
      3
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a central gateway to 170+ offline mock MCP servers with deterministic fixture-based responses and per-server SQLite state, enabling realistic credential-free agent trajectory testing and multi-step workflow rehearsal.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides structured MCP tools for local runtime observability and debugging of React Native/Expo apps on Android, enabling evidence-first diagnostics such as screenshots, UI trees, per-request network capture, performance metrics, and CDP-based console/heap/profiling exports.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to launch and manage an owned Mindustry runtime, create logic fixtures, configure processors with mlog programs, observe live memory values, and verify program replacements with digest preconditions.
      3 npm
      1
      -

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with the qa_get_* family splitting out entitlement, usage, session, round, attempts, ratings, and sync status. A few could cause mild confusion—get_app_snapshot overlaps with individual getters, and get_attempts vs get_round_detail both touch attempt data—but the descriptions provide enough separation.

    Naming Consistency5/5

    All tools share a consistent qa_ prefix and use snake_case verb_object naming: qa_get_* for reads, qa_set_*/qa_reset_*/qa_seed_*/qa_force_* for fixture mutations, and qa_validate_* for contract checks. The pattern is uniform and predictable.

    Tool Count4/5

    Eighteen tools is on the heavier side for a typical MCP server, but the count is justified by the QA instrumentation scope: many read-only truth endpoints plus a distinct fixture control-plane group. There is no obvious filler or redundancy that would make the set feel bloated.

    Completeness4/5

    The surface covers health, entitlement/usage, session/round/attempt data, skill/memory ratings, sync status, contract validation, and test-user fixtures. Minor gaps exist—such as no explicit create-test-user tool or read-back for seeded questions—but the core QA and test-fixture workflows are well supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues