Skip to main content
Glama

Related Servers

Alternatives to dmcheck-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to act as dynamic dungeon masters for text-based RPGs with dynamically generated rule systems and comprehensive game state management.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents consult a human-approved, versioned rulebook mined from team conversations and gate actions through deterministic checks for act, approval, or escalation. It also re-checks running actions before each step and after completion, halting runs that exceed approved rules or use stale or reused decisions.
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      An authoritative MCP server for long-form tabletop narrative play, managing campaign state, phases, revisions, and tool exposure while delegating semantic review and narration to Agent/Skill procedures.
      -
    • A
      license
      A
      quality
      D
      maintenance
      A MCP server enabling LLMs to roll dice
      1
      4
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Constitutional MCP server enforcing 13 Floors of governance for AI agents, providing tools for session anchoring, reasoning, safety critique, and audit logging.
      AGPL 3.0
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables multi-agent debate cross-examination and consensus arbitration through a deterministic, zero-dependency MCP server, providing structured outputs and telemetry for autonomous AI workflows.
      -

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are completely distinct: 'run' executes the analysis and returns findings, while 'rules' simply provides the rule set. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both names are short, lowercase, and readable, but 'run' is a verb while 'rules' is a noun, so they don't follow a uniform verb_noun pattern. Despite that, the naming is simple and not chaotic.

    Tool Count4/5

    With only 2 tools, the server is slightly under the typical 3-15 range, but the domain is narrowly scoped to checking transcripts against a rule set. The count feels appropriate for the purpose, with no unnecessary extras.

    Completeness5/5

    The tool set fully covers the domain: 'rules' provides the rule definitions, and 'run' applies them to a transcript. There are no obvious missing operations for a read-only checking service.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data