Skip to main content
Glama
Sign In
rilhia

PodQuery

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to PodQuery

No user-submitted related servers found.

    Related Servers

    • LibreLink MCP Server

      amansk
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to securely access FreeStyle LibreLink continuous glucose monitoring data, providing real-time readings, historical analysis, and health insights through natural language queries.
      8
      15
      MIT

    • SuperGlookoQuery

      sikcapri
      A
      license
      A
      quality
      A
      maintenance
      SuperGlookoQuery is a Claude Desktop extension (MCPB) that connects to Glooko diabetes device data and exposes it as clinical analysis tools (time in range, GMI, trends, enriched bolus/basal analysis, charting), for any pump/CGM combination Glooko supports rather than one fixed device. It's a fork of Richard Hall's podquery-mcp, reworked to discover each account's own data shape rather than assumi
      17
      MIT

    • dexcom-mcp

      sobek34
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading real-time continuous glucose monitor data from Dexcom sensors via the Share API, allowing Claude to access glucose levels, trends, and statistics.
      -
    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 12 tools

    Disambiguation4/5

    Each tool has a largely distinct purpose, and the descriptions actively cross-reference one another (e.g. summary vs trend, glucose vs chart_series, daily_insulin vs event-summed bolus). The main risk is the pair get_chart_html (renders/displays a chart) vs get_chart_series (returns chart data), which both target charting and could be misselected, though the text strongly differentiates them.

    Naming Consistency5/5

    All twelve tools follow a single consistent snake_case get_<noun> pattern (get_glucose, get_trend, get_basal_delivery, get_chart_series, etc.). There are no verb-style or case-style deviations anywhere.

    Tool Count5/5

    Twelve tools sit squarely in the well-scoped 3-15 range and each covers a distinct resource or aggregation on the diabetes domain. Nothing appears redundant or bolted-on.

    Completeness5/5

    The surface comprehensively covers the domain: raw and aggregate glucose, bolus (enriched), basal states, per-day insulin totals, carbs, settings history, device events, meal-window drill-down, and both data and rendered chart outputs. Read-only scope is appropriate for a query server, so no meaningful lifecycle gaps exist.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources