Skip to main content
Glama
PBS MCP AI Enabled API Server

PBS MCP AI Enabled API Server

by matthewdcage

Related Servers

Alternatives to PBS MCP AI Enabled API Server

No user-submitted related servers found.

    Related Servers

    • 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.
      91 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server providing AI assistants with access to healthcare data tools, including FDA drug information, PubMed research, health topics, clinical trials, and medical terminology lookup.
      7
      39 npm
      131
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for querying drug information from the OpenFDA API. Features Retrieve drug label information by brand name Retrieve drug information by generic (active ingredient) name Get all brand versions of a generic drug Get adverse event (side effect) reports for a drug
      7
      24 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants and MCP clients to query authoritative medical APIs for drug information, health statistics, medical literature, clinical guidelines, clinical trials, and pediatric resources. Runs locally without API keys, providing private access to sources such as FDA, WHO, PubMed, RxNorm, and Google Scholar.
      91 npm
      ISC
    • A
      license
      A
      quality
      D
      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

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose, making it impossible for an agent to misselect between non-existent alternatives.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'pbs_api' follows a straightforward and descriptive pattern without any conflicting conventions.

    Tool Count2/5

    A single tool is too few for the apparent scope of accessing a comprehensive API for medicines, pricing, and availability. This minimal toolset likely forces multiple functionalities into one tool, which can be confusing and inefficient for agents trying to perform specific operations like searching, filtering, or retrieving detailed information.

    Completeness2/5

    The tool surface is severely incomplete for the domain of pharmaceutical benefits information. A single tool cannot adequately cover the expected operations such as searching medicines, retrieving pricing details, checking availability, or filtering by criteria, leading to significant gaps that will cause agent failures in complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues