dod-mcp
Related Servers
Alternatives to dod-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.81MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- FlicenseNot gradedqualityDmaintenanceEnables spec-driven development acceptance gate with structured receipts, audit logs, and reviewer-ready evidence.-
- AlicenseNot gradedqualityCmaintenanceEnables 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.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables to extract project handover evidence and check material completeness against requirements without making approval decisions.-
- AlicenseNot gradedqualityBmaintenanceEnables deliverable conformance and evidence-chain checks by turning requirements into executable specs, validating numbers against a provenance ledger, and auditing PDF/OOXML metadata and archive manifests.38 npm1MIT
TDQS
Scored across 4 tools
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.
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.
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.
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.