Evidenceline
Related Servers
Alternatives to Evidenceline
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to screen lab results against published criteria with deterministic Python, search Australian contaminated-land guidance with cited passages, and draft guarded results sections whose numbers and citations are validated. All four tools are read-only and keep figures and citations under code control for a qualified person to check.4MIT
- FlicenseNot gradedqualityAmaintenanceEnables researchers and AI assistants to verify bibliographic existence and metadata consistency across multiple sources, score matches explainably, and inspect results without overwriting source files.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants and researchers to verify bibliographic records against multiple metadata sources, detect identifier conflicts, and review explainable match outcomes without destructively editing source files.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to validate CSV exports against schemas, infer schemas from example files, profile datasets, and diff before/after exports for lab/LIMS data-quality checks.MIT
- FlicenseNot gradedqualityCmaintenanceEnables converting PDFs and CSV/spreadsheet files into spreadsheets, extracting bank statement or receipt data into clean CSV, cleaning messy CSV, and generating client-ready reports through an open MCP endpoint.-
- 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.69 npm1MIT
TDQS
Scored across 9 tools
Each tool owns a distinct task: data tidy/QA, review-item drill-down, per-well retrieval, limit lookup, rule comparison, paragraph checking, number filling, document search, and redaction reporting. The closest pairs (get_results vs tidy_lab_files and lookup_limit vs search_guidelines) are clearly separated by workflow step and output type.
All nine tool names follow the same lowercase snake_case verb_noun pattern, from tidy_lab_files to show_redactions. Minor plural/singular variation such as get_results vs get_review_item is natural and does not break the convention.
Nine tools is well within the ideal range and each one maps to a distinct step in the evidence-to-report workflow. The count feels deliberately scoped rather than padded or thin.
The core workflow is well covered: data ingestion/QA, review item drill-down, results retrieval, guideline comparison, report number filling, paragraph verification, document search, and redaction reporting. The main gap is that soil guideline values such as HIL A are only searchable as document passages rather than available through a structured lookup like the drinking-water values, so some soil reporting tasks require manual reading of cited pages.