Skip to main content
Glama
onatozmenn

KlinikMCP

by onatozmenn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to KlinikMCP

No user-submitted related servers found.

    Related Servers

    • MedBridge

      MYASHWANTHREDDY
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives LLMs live access to clinical trials, FDA drug recalls, adverse-event reports, drug labels, and drug-name normalization via six validated tools.
      6
      MIT

    • medical-mcp

      samson-art
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server provides authoritative medical data from FDA, WHO, PubMed, RxNorm, and Google Scholar, enabling drug information lookup, health statistics retrieval, medical literature searching, and clinical guidelines access directly in AI workflows.
      75 npm
      MIT

    • OpenFDA MCP Server

      colbyw5
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query U.S. FDA public datasets, including drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory information.
      10
      MIT

    • Medical MCP Server

      geo07mz
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive medical information by querying authoritative APIs including FDA, WHO, PubMed, RxNorm, and Australia's PBS, enabling drug searches, health statistics, medical literature, drug nomenclature, and PBS subsidy queries.
      75 npm
      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

    A3.8/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have distinct purposes, though 'check_drug_interactions' and 'get_drug_interactions' could be confused without careful reading of descriptions. Overall, tools are well-differentiated.

    Naming Consistency3/5

    Names mix verb-noun patterns (e.g., check_drug_interactions, find_drug_equivalents) with noun-only names (e.g., body_surface_area, creatinine_clearance), lacking a uniform convention.

    Tool Count5/5

    18 tools cover a broad range of pharmaceutical and clinical functionalities without being excessive, appropriate for the domain's complexity.

    Completeness4/5

    The set covers core areas (calculations, interactions, labels, safety, search) but lacks some specialized features like allergy checks or multi-drug interaction checks, though not essential for the primary use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources