Ext Ops Panel
Open dashboard
Comparison

OpenFault vs DevHelm MCP Server

OpenFault is an MCP server published by OpenFault. Marketplaces we read that list it: 1 (Official MCP Registry). DevHelm MCP Server is an MCP server published by devhelmhq. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-12. 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

Where each is published
MarketplaceOpenFaultDevHelm MCP Server
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (PyPI): 128
Downloads/week (PyPI): 48
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.8.0
Downloads/month (PyPI): 128
Downloads/week (PyPI): 48
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

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

OpenFault vs DevHelm MCP Server
FactOpenFaultDevHelm MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Not statedOn your machine (devhelm-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/openfault/openfaultgithub.com/devhelmhq/mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-11-082026-10-11

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

OpenFault

In its own words, on Official MCP Registry:

Self-hosted, Sentry-compatible error tracker. Agents read and triage issues over MCP.

DevHelm MCP Server

In its own words, on Official MCP Registry:

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

How to run each

OpenFault

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

DevHelm MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DEVHELM_API_TOKEN=<YOUR_DEVHELM_API_TOKEN>" --transport stdio devhelm-mcp-server -- uvx devhelm-mcp-server

Requires: DEVHELM_API_TOKEN (secret)

Commands 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 OpenFault publish no settings it asks for, so we do not compare settings.

What it can do: OpenFault · What it can do: DevHelm MCP Server · 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.

Where the data comes from: how the catalog is built