Skip to main content
Glama
fabianofilho

anvisa-mcp

by fabianofilho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to anvisa-mcp

No user-submitted related servers found.

    Related Servers

    • openfda-mcp-server

      ek-nath
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.
      2
      MIT

    • ANVISA: Bulário Eletrônico

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying the official ANVISA electronic drug bulletin from a trusted source. It provides a single read-only tool for consulting drug information through natural language in any MCP-compatible client.
      MIT

    • fda-mcp

      Limecooler
      A
      license
      A
      quality
      D
      maintenance
      Provides LLM-optimized access to FDA data through the OpenFDA API and direct regulatory decision document retrieval, covering all 21 OpenFDA endpoints plus 510(k) summaries, De Novo decisions, and PMA approvals.
      4
      1
      MIT

    • Unofficial FDA MCP Server

      openpharma-org
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides comprehensive pharmaceutical intelligence by integrating real-time openFDA data with locally-cached Orange Book and Purple Book databases. It enables users to analyze drug safety, patents, generic equivalents, biosimilars, and regulatory information through natural language queries.
      3
      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

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools operate in completely separate domains: one retrieves recent Class III/IV medical devices with AI classification, the other queries drug registration status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern in Portuguese: buscar_samd_recentes and consultar_status_medicamento. The naming is clean, descriptive, and consistent.

    Tool Count3/5

    With only two tools, the server feels thin for the broad regulatory scope of Anvisa. The count is borderline acceptable because each tool covers a distinct product category, but it leaves many common regulatory queries unaddressed.

    Completeness2/5

    The device tool only covers recent SaMD registrations with a heuristic AI filter, and the drug tool only checks registration status. There are significant gaps such as searching devices by name/number, retrieving full regulatory details, or covering other Anvisa-regulated product types.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources