Skip to main content
Glama
Sign In
bag-health-mcp

bag-health-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bag-health-mcp

No user-submitted related servers found.

    Related Servers

    • i14y-mcp

      malkreide
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.
      13
      34 PyPI
      MIT

    • swiss-electricity-mcp

      malkreide
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Swiss electricity data from three official sources — production mix, consumption forecast, storage-lake fill, consumer price index, tariffs per municipality, and dataset discovery. Zero authentication.
      12
      27 PyPI
      MIT

    • ch-eli-mcp

      matematicsolutions
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Swiss federal legislation metadata via Fedlex, enabling search and retrieval of act details with ELI URIs, SR numbers, and multilingual support.
      3
      30 PyPI
      Apache 2.0
    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.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    The tools are mostly distinct, but the term 'series' appears in list_series, get_series_details, and get_indicator_series, which could cause slight confusion. Descriptions clearly differentiate sources (BAG IDD vs Obsan/other indicators), so an attentive agent can tell them apart.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern with the same prefix, e.g. list_diseases, get_disease_data, download_export. No deviations or mixed conventions.

    Tool Count5/5

    10 tools is well within the ideal range for a data-access server; each tool serves a clear purpose in discovery, metadata, or retrieval, with no obvious redundancy.

    Completeness4/5

    The surface covers full workflows for both disease surveillance (list -> series -> details -> data) and indicators (search -> fetch), plus bulk export and versioning. A minor gap is the lack of a dedicated 'list all indicators' tool, but search likely covers this.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources