Skip to main content
Glama

Related Servers

Alternatives to dod-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables agents and developers to manage requirements, acceptance criteria, evidence, and append-only decisions, and computes whether each requirement is verified, stale, or unverified based on code changes and supporting evidence.
      8
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to check whether procedures are current and whether actions have the stored evidence needed for human review, returning status, citations, and blockers through read-only MCP tools while always requiring human review.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a requester's AI delegate and an assignee's coding agent to settle whether a task is done on a shared board, exchanging only typed messages (contract, question, answer, evidence, verdict) instead of ticket comments. It enforces a verifiable done contract with required evidence, re-runs checks to verify that evidence, bounds negotiation to three rounds, and escalates to the humans in a single batched notification when the mandate runs out.
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables to extract project handover evidence and check material completeness against requirements without making approval decisions.
      -

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct verb-purpose: get_dod retrieves criteria, check_dod validates collected evidence, lint_acceptance_criteria validates AC text, diff_dod compares versions. The only mild overlap is get_dod's no-argument mode (listing task types) and its role as the prerequisite for check_dod, but descriptions make the pipeline order explicit.

    Naming Consistency5/5

    All four names follow a clean verb_noun snake_case pattern (get_, check_, lint_, diff_), with the DoD-related tools sharing a consistent _dod suffix. No mixed conventions or casing.

    Tool Count4/5

    Four tools is small but each covers a genuinely different operation in a narrow read-only domain, so nothing feels padded. It is on the thin side — no write/attestation tools exist — but that appears intentional for a read-only DoD reference service.

    Completeness3/5

    The read-only lifecycle (fetch criteria, check evidence, lint AC, diff versions) is covered, but check_dod returns needs_judgment pointing at rubric://dod/{type} and lint points at template://{type} with no tool to retrieve either, creating dead ends unless resources fill the gap. There is also no way to record judgment outcomes or attestations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues