Skip to main content
Glama
obseard223

tempstick-mcp

by obseard223
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tempstick-mcp

No user-submitted related servers found.

    Related Servers

    • IoT MCP Server

      Duke-CEI-Center
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to read sensor data from IoT devices and dispatch data collection tasks through a unified interface supporting multiple protocols.
      17
      -

    • whoop-ai-mcp

      fZimmermann03
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query recovery, sleep, HRV, strain, workouts, and personal health analytics in natural language through supported AI assistants, using read-only tools for daily status, baselines, trends, and period comparisons.
      7 npm
      -

    • Mender MCP Server

      pasinskim
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.
      2
      MIT

    • AlertOps MCP Server

      WYRE-AI
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.
      11
      Apache 2.0

    • cubepilot

      dreaddy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and control a homee smart home in natural language: listing devices and their values, switching, dimming or moving them, and viewing or editing homeegrams. Also covers backups, device swaps across all automations, device history, and the homee diary, with all writes subject to the same backups, read-only mode and audit log as the web UI.
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Core tools (list_sensors, get_sensor, get_readings_history, get_alerts) target distinct resources, but get_freezer_status overlaps with three of them by bundling latest reading, history summary, and alerts. Its composite 'is it OK?' purpose is clearly described, so an agent can usually distinguish when to use it.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern: list_sensors, get_sensor, get_readings_history, get_alerts, and get_freezer_status. The singular/plural distinction in list_sensors and get_sensor is predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a sensor monitoring integration. Each tool has a plausible role, and the set avoids both thinness and bloat.

    Completeness4/5

    The surface covers the main read-only workflows: listing sensors, fetching latest readings, summarizing history, checking alerts, and a one-call status helper. Minor gaps exist around alert state changes or sensor configuration, but these may be outside the API's intended scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources