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

    • saudeemdado-mcp

      pedropaulofernandes88-stack
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of Brazilian public health indicators from DataSUS microdata — mortality, dengue, hospitalizations, ICSAP, and births — through 41 tools covering consultation, analysis (peer-stratum comparison, dengue endemic channel, weekly bulletin), reliability warnings, and anomaly detection. It runs locally against the public API with anti-hallucination rules so every figure comes from a tool with its source cited.
      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
    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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly separated by target entity: one queries medicine registrations, the other lists recent Class III/IV medical devices with AI classification. There is no functional overlap or plausible confusion between them.

    Naming Consistency5/5

    Both tool names follow a consistent Portuguese snake_case verb-first pattern: 'consultar_' and 'buscar_'. The structure is predictable and matches the action each tool performs.

    Tool Count3/5

    With only two tools, the server feels thin for a domain as broad as Anvisa regulatory data. The tools are meaningful and well-scoped, but the count sits at the low end of the borderline range.

    Completeness2/5

    The server covers only two narrow queries: medicine status lookup and recent device listings. It lacks many obvious operations for a regulatory database, such as querying devices by name/registration, retrieving full registration details, or tracking changes over time.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources