Skip to main content
Glama
chaoz23

dmcheck-mcp

by chaoz23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dmcheck-mcp

No user-submitted related servers found.

    Related Servers

    • DMCP

      shawnrushefsky
      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.
      8 npm
      12
      MIT

    • SagaSmith Narrative

      SagaSmithAI
      F
      license
      Not graded
      quality
      A
      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.
      -

    • mcp-dice

      yamaton
      A
      license
      A
      quality
      D
      maintenance
      A MCP server enabling LLMs to roll dice
      1
      4
      MIT

    • arifosmcp

      ariffazil
      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

    • Railroaded

      kimosahy
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server enabling AI agents to autonomously play D\&D as players and Dungeon Masters, with real dice rolls and full campaign management.
      2
      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

    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

    ActivitySlowing
    ResponsivenessWithin a week

    Resources