DicksonOne MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.0.1Updated Nov 7, 2026

List alerts and data loggers, count active alerts, and acknowledge alerts in DicksonOne.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableSecurity & Monitoring Data & Analytics

Server details

Identifier: io.usefulapi/dicksonone
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Nov 7, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fdicksonone.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fdicksonone?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted MCP server for DicksonOne that lets an assistant list monitoring alerts and data loggers, count active alerts, and acknowledge alerts.

What you can do: Check the connected DicksonOne account and user behind the API key
List alerts with severity, type, excursion and return-to-normal times, filterable by logger, location, severity, type, active state or time window
Count active and cleared alerts and break them down by severity
Read the comments users added to a single alert
List locations and data loggers, including archived or replaced loggers, to get the ids and tokens used for filtering
Acknowledge an alert, recorded against the token's user and server time
When to use it: Useful when you want to ask about temperature or other environmental excursions in DicksonOne from a chat client: which alerts are still active, which sites or fridges they belong to, what people commented, and closing out an alert after review.
Requirements: A remote endpoint reached over streamable HTTP; no local install. Sign-in is via OAuth, and the login page asks for a DicksonOne API key (created in DicksonOne under Manage, then API Keys), which the server validates and stores per user. Only the URL goes in the client config. A free plan allows 50 tool calls per month; paid plans are available.

Before you install

Acknowledging an alert writes to DicksonOne and is attributed to the token's user, so confirm before running it; already-acknowledged alerts return an error. Your DicksonOne API key is entered on the hosted login page and stored by the provider, so trust in that third party matters. Usage is metered, and upgrade tools return Stripe Checkout links for paid plans that charge money; cancellation has no refund for the current period.

Installation

In SourceWeft

Open DicksonOne MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fdicksonone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dicksonone-by-usefulapi": {
      "type": "http",
      "url": "https://dicksonone.usefulapi.io/mcp"
    }
  }
}

README

DicksonOne MCP by usefulapi

Use your DicksonOne account from Claude, Cursor, or any MCP client. List alerts and data loggers, read alert comments, and acknowledge alerts. Hosted, no local install: connect with your own credentials.

Live endpoint: https://dicksonone.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://dicksonone.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http dicksonone https://dicksonone.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your DicksonOne credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/dicksonone/

On first connect you provide a DicksonOne API key (DicksonOne → Manage → API Keys). The server validates it and stores it per user. No keys go in config files.

Tools

Tool	Type	What it does
`dicksonone_whoami`	read	Who am I
`dicksonone_list_alerts`	read	List alerts
`dicksonone_get_alert_summary`	read	Alert counts
`dicksonone_list_alert_comments`	read	List alert comments
`dicksonone_list_locations`	read	List locations
`dicksonone_list_devices`	read	List data loggers
`dicksonone_acknowledge_alert`	write	Acknowledge an alert
`dicksonone_usage_status`	meta	Usage status (free-tier meter)
`dicksonone_request_feature`	meta	Request a missing feature
`dicksonone_upgrade`	meta	Upgrade to Pro or Pro+
`dicksonone_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with dicksonone_upgrade (it returns a Stripe Checkout link). Cancel any time with dicksonone_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running dicksonone_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/dicksonone/README.md at commit 2450437

Tools

dicksonone_whoami

Who am I

Return the DicksonOne user that the API token belongs to. Good first call to confirm the connection. REST API: GET /api/rest/whoami.

Takes no parameters.

dicksonone_list_alerts

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. REST API: GET /api/rest/alerts.

Parameterstypeactivetokensseveritypage_sizechannel_idsended_afterpage_numberended_beforelocation_idsstarted_afterstarted_before

dicksonone_get_alert_summary

Alert counts

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.

Parameterstypeactivetokensseveritychannel_idsended_afterended_beforelocation_idsstarted_afterstarted_before

dicksonone_list_alert_comments

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.

Parametersalert_idrequiredpage_sizepage_number

dicksonone_list_locations

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.

Parametersidsnamepage_sizepage_number

dicksonone_list_devices

List data loggers

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.

Parametersnamepage_sizepage_numberinclude_archivedinclude_replacements

dicksonone_acknowledge_alert

Acknowledge an 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.

Parametersalert_idrequired

Version history

v1.0.1LatestNov 7, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

5 toolsNov 7, 2026

Plan	Price	Limit
Free	$0	50 tool calls / month
Pro (per user)	$9/mo or $90/yr (2 months free)	Unlimited*