DevHelm MCP Server
PYPI · DEVHELM-MCP-SERVER · SCANNED SEP 21
Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5203 tokens (~49/item across 106 items; 106 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 1% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 26 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_monitor" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 107 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the DevHelm MCP Server server?
DevHelm MCP Server runs locally as a PyPI package, launched with uvx devhelm-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · devhelm-mcp-server
claude mcp add devhelmhq-mcp-server -- uvx devhelm-mcp-server
{
"mcpServers": {
"devhelmhq-mcp-server": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
]
}
}
} {
"servers": {
"devhelmhq-mcp-server": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
]
}
}
} codex mcp add devhelmhq-mcp-server -- uvx devhelm-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"devhelmhq-mcp-server": {
"type": "local",
"command": [
"uvx",
"devhelm-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add devhelmhq-mcp-server --command uvx --arg devhelm-mcp-server
mcp_servers:
devhelmhq-mcp-server:
command: "uvx"
args: ["devhelm-mcp-server"] {
"McpServers": {
"devhelmhq-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"devhelm-mcp-server"
]
}
}
} assistant mcp add devhelmhq-mcp-server -t stdio -c uvx -a devhelm-mcp-server
{
"mcpServers": {
"devhelmhq-mcp-server": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/devhelm-mcp-server@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_status_page_component Update Status Page Component ~46
Update a status page component's name, group, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| component_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_status_page_group Update Status Page Group ~42
Update a component group's name or display order.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| group_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_status_page_incident Update Status Page Incident ~47
Update a status page incident's title, impact, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| incident_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_tag Update Tag ~27
Update a tag.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| tag_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_webhook Update Webhook ~29
Update a webhook endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| webhook_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
verify_status_page_domain Verify Status Page Domain ~43
Trigger DNS verification for a custom domain. Returns the updated domain with current verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
What is the DevHelm MCP Server server?
DevHelm MCP Server is listed in the public MCP registry as io.github.devhelmhq/mcp-server. Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm. This page covers its PyPI package (devhelm-mcp-server).
Is the DevHelm MCP Server server safe to use?
DevHelm MCP Server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DevHelm MCP Server server expose?
DevHelm MCP Server exposes 106 tools: list_monitors, get_monitor, create_monitor, update_monitor, delete_monitor, and 101 more. Their descriptions and schemas cost roughly 5,067 tokens of context every time the server is loaded.
Is the DevHelm MCP Server server still maintained?
DevHelm MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.