tempstick-mcp
Related Servers
Alternatives to tempstick-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to read sensor data from IoT devices and dispatch data collection tasks through a unified interface supporting multiple protocols.17-
- FlicenseNot gradedqualityAmaintenanceEnables 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.14 npm-
- AlicenseAqualityBmaintenanceEnables AI assistants to read live temperature and Pt100 resistance measurements, sampled statistics, and device information from a Senseca PRO 111/PRO 115 USB thermometer, with optional write tools for setting the instrument clock and location labels.445 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to control and monitor Tesla vehicles via natural language through the Tessie API, supporting battery, climate, security, charging, and more.611MIT
- AlicenseAqualityBmaintenanceEnables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.11Apache 2.0
TDQS
Scored across 5 tools
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.
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.
Five tools is well-scoped for a sensor monitoring integration. Each tool has a plausible role, and the set avoids both thinness and bloat.
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.