Temp Stick MCP by usefulapi is an MCP server published by io.usefulapi, hosted at temp-stick.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including tempstick_list_sensors, tempstick_get_sensor, tempstick_get_readings, tempstick_list_alerts.
Read temperature and humidity sensors, their readings and alert notifications in Temp Stick.
4,265 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
List the Temp Stick sensors on the account with their names, ids and last and next check-in times (UTC). Good first call to find sensor ids. Temp Stick API: GET /sensors/all.
No parameters.
{
"name": "tempstick_list_sensors",
"title": "List sensors",
"description": "List the Temp Stick sensors on the account with their names, ids and last and next check-in times (UTC). Good first call to find sensor ids. Temp Stick API: GET /sensors/all.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List sensors",
"readOnlyHint": true
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Get one Temp Stick sensor's details, including its name and check-in times. Temp Stick API: GET /sensor/{sensor_id}.
| Parameter | Type | Description |
|---|---|---|
| sensor_id * | string | The sensor id, for example TS00ABC123 (from tempstick_list_sensors). |
{
"name": "tempstick_get_sensor",
"title": "Get a sensor",
"description": "Get one Temp Stick sensor's details, including its name and check-in times. Temp Stick API: GET /sensor/{sensor_id}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"sensor_id"
],
"properties": {
"sensor_id": {
"type": "string",
"minLength": 1,
"description": "The sensor id, for example TS00ABC123 (from tempstick_list_sensors)."
}
}
},
"annotations": {
"title": "Get a sensor",
"readOnlyHint": true
}
}Get the readings of one sensor: temperature in Celsius, humidity, voltage, RSSI and sensor_time (UTC). `setting` picks the time range; the vendor example uses 24_hours. Temp Stick API: GET /sensor/{sensor_id}/readings.
| Parameter | Type | Description |
|---|---|---|
| offset | integer | Query offset as the vendor example uses it (21600). The vendor docs do not state its unit. |
| setting | string | Time range, for example 24_hours (the default). Other values are not listed by the vendor docs. |
| sensor_id * | string | The sensor id, for example TS00ABC123 (from tempstick_list_sensors). |
{
"name": "tempstick_get_readings",
"title": "Get sensor readings",
"description": "Get the readings of one sensor: temperature in Celsius, humidity, voltage, RSSI and sensor_time (UTC). `setting` picks the time range; the vendor example uses 24_hours. Temp Stick API: GET /sensor/{sensor_id}/readings.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"sensor_id"
],
"properties": {
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Query offset as the vendor example uses it (21600). The vendor docs do not state its unit."
},
"setting": {
"type": "string",
"description": "Time range, for example 24_hours (the default). Other values are not listed by the vendor docs."
},
"sensor_id": {
"type": "string",
"minLength": 1,
"description": "The sensor id, for example TS00ABC123 (from tempstick_list_sensors)."
}
}
},
"annotations": {
"title": "Get sensor readings",
"readOnlyHint": true
}
}List the alert notifications on the account with the sensor id, the alert message and the created time (UTC). Temp Stick API: GET /user/notifications.
No parameters.
{
"name": "tempstick_list_alerts",
"title": "List alert notifications",
"description": "List the alert notifications on the account with the sensor id, the alert message and the created time (UTC). Temp Stick API: GET /user/notifications.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List alert notifications",
"readOnlyHint": true
}
}Tools for Temp Stick, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "Which of our temperature sensors have not checked in recently?"; "Show the last 24 hours of readings for the freezer sensor."; "List the temperature alert notifications from this week.". Read-only tools never change data; ask the user before a tool that creates, changes or deletes Temp Stick data. Free plan: 50 tool calls per month. Run tempstick_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run tempstick_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run tempstick_upgrade without a plan: it returns both plans, each with a payment link for the user to open. tempstick_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.