Skip to main content
Glama
Sign In
Biomedical APIs MCP Server

Biomedical APIs MCP Server

by KrithikVishal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Biomedical APIs MCP Server

No user-submitted related servers found.

    Related Servers

    • medical-mcp

      GerhardHarris
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to query authoritative medical APIs for drug information, health statistics, clinical guidelines, trials, and literature from sources such as FDA, WHO, PubMed, RxNorm, and Google Scholar, running locally without API keys.
      97 npm
      ISC

    • medical-mcp

      fatimas7789
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to locally query authoritative medical sources like FDA, WHO, PubMed, RxNorm, and related APIs for drug information, health statistics, clinical guidelines, trials, and medical literature without API keys.
      97 npm
      ISC

    • medical-mcp

      juliafrancois5628
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI environments to query authoritative medical APIs for drug information, literature, health statistics, clinical guidelines, trials, and pediatric sources locally without API keys.
      97 npm
      ISC

    • 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.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct biomedical database or data type, with descriptions clearly differentiating their sources and functions. There is no overlapping purpose among the 14 tools.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern: 'get_' for direct retrieval, 'query_' for credentialed databases, and 'search_' for keyword queries. The prefixes are used consistently across the set.

    Tool Count5/5

    With 14 tools covering diverse biomedical data sources (compounds, activities, trials, literature, adverse events, clinical datasets), the count is well-scoped for the server's purpose without being excessive or thin.

    Completeness4/5

    The tool set covers major biomedical data domains, including compounds, bioactivities, trials, literature, and clinical datasets. Minor gaps exist (e.g., protein data, gene expression), but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources