DicksonOne MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/dicksonone and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 7 Nov 2026. Not supplied by the maker.

• 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

• 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 a

• 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