AOP MCP Server
Related Servers
Alternatives to AOP MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenancePublic MCP endpoint for physiologically based pharmacokinetic (PBPK) simulation, qualification, and dossier export.8Apache 2.0
- AlicenseBqualityBmaintenanceEnables biomedical research workflows via MCP, including experiment and document search, PDF text extraction, evidence retrieval, and validation with provenance tracking.10MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for maintaining specific Wikidata items (person, company, publications) with read tools and a two-step write workflow that enforces sourced, human-approved batch edits.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that reproduces the results of Nikitin et al., 'Towards Explainable Computational Toxicology: Linking Antitargets to Rodent Acute Toxicity' as callable tools, enabling users to compute toxicity predictions and mechanistic analyses deterministically from a bundled dataset.-
- 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
- AlicenseNot gradedqualityBmaintenanceAn MCP server for High-Throughput Screening (HTS) assay calculations across sub-cellular, cellular, tissue, and organism biological tiers, enabling local-first bioassay analysis.MIT
TDQS
Scored across 42 tools
The set contains multiple near-duplicate tools with overlapping purposes, especially the list_assays_for_aop vs get_assays_for_aop and list_assays_for_aops vs get_assays_for_aops pairs, plus three discover_orphan_stressors variants. An agent could easily misselect among assay discovery and draft-review/export tools despite descriptions. Some distinctions exist, but boundaries are blurred.
Most names follow a snake_case verb_noun pattern (get_aop, list_key_events, create_draft_aop), which is predictable. Some deviations like add_or_update_ke, plan_linear_draft_review_document, and trace_chemical_on_draft introduce minor inconsistency, and the list_/get_ synonym split weakens consistency.
42 tools is excessive for a single domain and includes many input-variant duplicates (single vs multiple AOPs, query vs explicit) that could be consolidated. This exceeds the 25+ threshold for 'too many' per the rubric.
The surface covers core AOP lifecycle operations: search/get AOPs, key events, KERs, assays, chemical mapping, draft creation, KE/KER editing, validation, evidence review, and export/audit. Missing delete/remove operations and draft-level metadata updates are minor gaps agents can work around.