Skip to main content
Glama
chrisvo

medlineplus-mcp

by chrisvo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to medlineplus-mcp

No user-submitted related servers found.

    Related Servers

    • Medical MCP Server

      ritaf0793
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, medical literature, health statistics, clinical guidelines, and pediatric resources through local MCP tools.
      82 npm
      ISC

    • mcp-medlineplus

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to MedlinePlus consumer health information from NIH, enabling free-text search across health topics.
      385 npm
      MIT

    • Healthcare MCP Server

      andrewsalopek1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to retrieve and search authoritative healthcare data, including FDA drug information, PubMed literature, health topics, clinical trials, ICD-10 terminology, medRxiv preprints, NCBI Bookshelf content, BMI calculations, and DICOM metadata.
      32 npm
      MIT

    • MCP Healthcare Server

      shinegami-2002
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to medical data including drug interactions, ICD-10 codes, FDA adverse event reports, and clinical guidelines. It enables LLMs to query databases like openFDA, PubMed, and CMS for pharmaceutical and clinical information.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The four specific lookup tools (medication, diagnosis, lab test, procedure) have clearly distinct purposes. However, medlineplus_connect is a low-level utility that overlaps with all of them, potentially causing confusion if an agent chooses it over the more specific tool.

    Naming Consistency3/5

    Four tools use a consistent 'lookup_' prefix, but medlineplus_connect breaks this pattern with a different naming style. The inconsistency is noticeable but not chaotic.

    Tool Count4/5

    Five tools is a reasonable number for the domain, covering the main clinical code systems (RXCUI, ICD, LOINC, CPT, SNOMED). The count is not excessive and fits the scope well.

    Completeness4/5

    The tools cover the major MedlinePlus lookup categories (medication, diagnosis, lab, procedure). The general medlineplus_connect tool fills potential gaps, though a dedicated health-topic search tool might be missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources