io.usefulapi/dicksonone · v1.0.2 · other
DicksonOne MCP by usefulapi is healthy: it completed an MCP handshake in 523 ms and exposes 7 tools.
List alerts and data loggers, count active alerts, and acknowledge alerts in DicksonOne.
Endpoint: https://dicksonone.usefulapi.io/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 7 |
| Latency | 523 ms |
| Last checked (UTC) | 2026-11-07T21:50:25.749Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-07T21:50:25.749Z | Healthy | 523 |
dicksonone_whoami | Return the DicksonOne user that the API token belongs to. Good first call to confirm the connection. REST API: GET /api/rest/whoami. |
dicksonone_list_alerts | List historical alerts for the account: a logger tripped a warning or excursion condition. Each alert has severity, type, excursion_at, returned_to_normal_at, acknowledged_at and its location, device and channel. Filter by logger, location, severity, type, active state or time window. Paginated. RES |
dicksonone_get_alert_summary | Count active and cleared alerts, and alerts by severity (excursion, warning), for the account or for a filtered set. REST API: GET /api/rest/alerts/summary. |
dicksonone_list_alert_comments | List the comments that users added to one alert, with author and time. Paginated. REST API: GET /api/rest/alerts/{alert_id}/comments. |
dicksonone_list_locations | List the locations (sites, rooms, fridges) on the account, with their sublocation ids. Use the ids to filter alerts. Filter by name or by a list of ids. Paginated. REST API: GET /api/rest/locations. |
dicksonone_list_devices | List the data loggers (devices) on the account. Each logger has a string token that stays the same across hardware replacements; use the token to filter alerts. Optionally filter by name and include archived or replaced loggers. Paginated. REST API: GET /api/rest/devices. |
dicksonone_acknowledge_alert | Acknowledge one alert. The API sets the acknowledger to the user of the token and the time to the server time. An alert that is already acknowledged returns HTTP 409; the tool reports that as an error, and nothing changes. REST API: POST /api/rest/alerts/{alert_id}/acknowledgements. |