DevHelm MCP Server vs DicksonOne MCP by usefulapi
DevHelm MCP Server is an MCP server published by devhelmhq. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). DicksonOne MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DevHelm MCP Server |   DicksonOne MCP by usefulapi |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 128 Downloads/week (PyPI): 48 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.2 No figure published Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.8.0 Downloads/month (PyPI): 128 Downloads/week (PyPI): 48 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | DevHelm MCP Server | DicksonOne MCP by usefulapi |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-07 |
| Where it runs (differs) | On your machine (devhelm-mcp-server) | Remote server (dicksonone.usefulapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/devhelmhq/mcp-server | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-11-07 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
DevHelm MCP Server
Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
DicksonOne MCP by usefulapi
List alerts and data loggers, count active alerts, and acknowledge alerts in DicksonOne.
How to run each
DevHelm MCP Server As a local MCP server: PyPI package
claude mcp add --env "DEVHELM_API_TOKEN=<YOUR_DEVHELM_API_TOKEN>" --transport stdio devhelm-mcp-server -- uvx devhelm-mcp-serverRequires: DEVHELM_API_TOKEN (secret)
DicksonOne MCP by usefulapi As a remote MCP server
claude mcp add --transport http dicksonone https://dicksonone.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of DicksonOne MCP by usefulapi publish no settings it asks for, so we do not compare settings.
What it can do: DevHelm MCP Server · What it can do: DicksonOne MCP by usefulapi · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.