ot-dossier-mcp
Related Servers
Alternatives to ot-dossier-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceReplay-verified minimal JSON reproductions and deterministic TypeScript/OpenAPI drift checks. Local-first CLI and MCP server.256 npm1Mozilla Public 2.0
- FlicenseBqualityDmaintenanceUnofficial Model Context Protocol server for accessing Open Targets platform data for gene-drug-disease associations research.611-
- AlicenseNot gradedqualityAmaintenanceEnables 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.55 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to verify citations and bibliographies and to check whether source documents support factual claims, using local inference, exact evidence provenance, and deterministic verdicts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables defining and verifying evidence contracts for claims in READMEs, releases, or product pages using constrained verifiers and generating hash-chained receipts and reports.5 npmMIT
- AlicenseBqualityAmaintenanceMCP server that exposes the Open Targets Platform GraphQL API as a set of tools for querying biomedical data such as targets, diseases, drugs, and genetic evidence.68266 PyPI19MIT
TDQS
Scored across 2 tools
The two tools have distinct verbs and roles: one assembles/replays evidence, the other validates references against an assembled packet. They are part of the same pipeline, which introduces mild sequencing ambiguity, but a careful reading of the descriptions clearly separates their purposes.
Both tools use snake_case with a leading verb (assemble_..., validate_...) and noun-phrase tails. The verb_noun pattern is consistent throughout, with no style mixing.
Only 2 tools is on the thin side, though the server's scope (a single frozen evidence dossier workflow) is narrow enough that this is borderline rather than clearly wrong. A few more operations would make it feel better scoped.
The surface covers an assemble-and-validate loop but appears locked to one hardcoded disease pair (NOD2/TNF and IBD) with no discovery, listing, or update operations, and no way to build or modify the underlying packet. Notable gaps remain for a general dossier workflow.