medterms-mcp
Related Servers
Alternatives to medterms-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceUnified MCP server providing LLMs with reliable lookup access to ICD-11, LOINC, RxNorm, MeSH, ATC, CID-10, and (optionally) SNOMED CT.33133 npm13MIT
- AlicenseBqualityDmaintenanceMCP server for mapping clinical terminology to OMOP concepts using LLMs, with vocabulary search and batch processing capabilities.240Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides access to the NIH UMLS API and the NIH VSAC FHIR API. This server enables AI models to search medical terminology, look up concept definitions, explore relationships between medical concepts, map codes between different medical coding systems, and work with curated clinical value sets.1MIT
- AlicenseAqualityDmaintenanceMCP server for automated ICD-10 medical coding. Code clinical text to ICD-10-CM diagnoses, search 74,000+ codes, and de-identify PHI via the AutoICD API.67 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server with 60 tools connecting AI assistants to Czech healthcare databases (SUKL, MKN-10, NRPZS) and global biomedical sources (PubMed, ClinicalTrials.gov, OpenFDA).1MIT
- FlicenseAqualityCmaintenanceThree composable MCP servers for clinical AI — FHIR R4 read/search/validate, medical terminology (LOINC/SNOMED/RxNorm/ICD-10), and drug safety reasoning (interactions, dose check, allergy). Apache-2.0, production-ready.5-
TDQS
Scored across 6 tools
Each tool targets a distinct terminology or function: lookup tools for specific vocabularies (ICD-10, MedDRA, CTCAE, RxNorm), a cross-mapping tool, and a general concept search. No overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (lookup_*, crossmap_*, search_*). The naming is predictable and clear.
6 tools is well-scoped for a medical terminology server, covering major coding systems and mappings without being excessive or insufficient.
Covers key terminologies (ICD-10, MedDRA, CTCAE, RxNorm) and provides a general search across multiple systems via UMLS. Minor gaps exist (e.g., direct LOINC lookups), but the set supports core pharmacovigilance and oncology workflows.