DevHelm MCP Server
PYPI · DEVHELM-MCP-SERVER
Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
Available components
Last scanned (13 hours ago)
Scores higher than 74% of PyPI servers
Category Monitoring and Observability
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 build step with no custom scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 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 4869 tokens (~45/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 Management83
- Stability observed for 25 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- Stability: 0.97 → pass security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 24 Oct 26 +5
- Source repository: unverified → pass ▲ security
- 23 Oct 26 −20
- Malware scan: pass → unverified ▼ security
- Provenance: pass → unverified ▼ security
- Stability: 0.97 → pass security
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 7 Nov 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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| 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 →
get_status_page_incident Get Status Page Incident ~39
Get a status page incident with its full timeline of updates.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_tag Get Tag ~22
Get a tag by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_webhook Get Webhook ~24
Get a webhook endpoint by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_alert_channels List Alert Channels ~18
List all alert channels configured in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_api_keys List Api Keys ~17
List all API keys in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_dependencies List Dependencies ~14
List all tracked service dependencies.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_environments List Environments ~16
List all environments in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_incidents List Incidents ~16
List all incidents in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_maintenance_windows List Maintenance Windows ~164
List maintenance windows for the workspace. Use this BEFORE creating a new window to check whether someone else (or an earlier agent run) already scheduled overlap, or AFTER a deploy to confirm the window you opened is still active. Filters (all optional; combine freely): - ``monitor_id``: UUID of a monitor — only windows attached to that single monitor (org-wide windows are excluded). - ``status``: ``"active"`` for windows currently in progress, or ``"upcoming"`` for windows scheduled in the future. Past / cancelled windows are not returned by the API today; omit ``status`` for the broadest result.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_monitor_results List Monitor Results ~40
List recent check results for a monitor (cursor-paginated).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | – | – | – |
| monitor_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_monitor_rule_evaluations List Monitor Rule Evaluations ~73
List rule evaluations produced for a monitor (paginated).
| Name | Type | Req | Description |
|---|---|---|---|
| from_ | – | – | – |
| monitor_id | string | yes | – |
| only_matched | – | – | – |
| page | integer | – | – |
| region | – | – | – |
| rule_type | – | – | – |
| size | integer | – | – |
| to | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_monitor_transitions List Monitor Transitions ~106
List state transitions recorded for a monitor (paginated). A transition captures every WATCHING→TRIGGERED→CONFIRMED→RESOLVED edge the detection engine walked. Includes transitions that occurred before an incident was declared (incident_id = null). Use to reconstruct the full reliability history of a monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| from_ | – | – | – |
| monitor_id | string | yes | – |
| page | integer | – | – |
| size | integer | – | – |
| to | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_monitor_versions List Monitor Versions ~38
List version history for a monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| page | integer | – | – |
| size | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_monitors List Monitors ~17
List all uptime monitors in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_notification_policies List Notification Policies ~18
List all notification policies in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_resource_groups List Resource Groups ~17
List all resource groups in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_secrets List Secrets ~21
List all secrets (metadata only, values are never returned).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_page_components List Status Page Components ~26
List all components on a status page.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_page_domains List Status Page Domains ~26
List custom domains on a status page.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_page_groups List Status Page Groups ~30
List component groups on a status page (with nested components).
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_page_incidents List Status Page Incidents ~43
List incidents on a status page (paginated).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_id | string | yes | – |
| size | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_page_subscribers List Status Page Subscribers ~44
List confirmed subscribers on a status page (paginated).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_id | string | yes | – |
| size | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_status_pages List Status Pages ~17
List all status pages in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_tags List Tags ~15
List all tags in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_webhooks List Webhooks ~17
List all webhook endpoints in the workspace.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
pause_monitor Pause Monitor ~26
Pause a monitor (stops checking until resumed).
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
post_status_page_incident_update Post Status Page Incident Update ~75
Post a timeline update on a status page incident. Required fields: body (message text), status. Optional: notifySubscribers (default true), affectedComponents (list of {componentId, 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.
publish_status_page_incident Publish Status Page Incident ~70
Publish a draft incident (sets it live, notifies subscribers). Use update_status_page_incident first if you need to change the draft's title, impact, status, body, or affected components before publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
release_deploy_lock Release Deploy Lock ~25
Release a deploy lock by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| lock_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_resource_group_member Remove Resource Group Member ~34
Remove a monitor from a resource group.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
| member_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_status_page_domain Remove Status Page Domain ~35
Remove a custom domain from a status page.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_status_page_subscriber Remove Status Page Subscriber ~35
Remove a subscriber from a status page.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| subscriber_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reorder_status_page_components Reorder Status Page Components ~73
Reorder components on a status page. Required: positions — list of {componentId, position} entries giving every component its new zero-based ordinal. The full set must be provided; partial reorders are rejected by the API.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reorder_status_page_layout Reorder Status Page Layout ~156
Batch-reorder a status page's full layout. Required: sections — top-level layout in their new order, where each entry is either {kind:"component", componentId} or {kind:"group", groupId}. Use ``groupOrders`` (optional) to also reorder components within specific groups; only include groups whose internal order changed. The full top-level set must be provided — partial reorders are rejected by the API. Use this for "drag-and-drop" layout edits that touch both groups and ungrouped components. To reorder components within a single group only, prefer ``reorder_status_page_components``.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_incident Resolve Incident ~33
Resolve an active incident, optionally with a resolution message.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
| message | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
resume_monitor Resume Monitor ~21
Resume a paused monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
revoke_api_key Revoke Api Key ~29
Revoke an API key (disables it without deleting).
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
test_alert_channel Test Alert Channel ~30
Send a test notification to an alert channel to verify it works.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
test_monitor Test Monitor ~31
Trigger an ad-hoc test run for a monitor and return the result.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
test_notification_policy Test Notification Policy ~29
Send a test dispatch to verify a notification policy's routing.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
test_webhook Test Webhook ~30
Send a test event to a webhook endpoint to verify it works.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
track_dependency Track Dependency ~33
Start tracking a service dependency by its slug (e.g. 'github', 'aws').
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_alert_channel Update Alert Channel ~30
Update an existing alert channel.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| channel_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_environment Update Environment ~28
Update an environment by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_maintenance_window Update Maintenance Window ~233
Update an in-flight or scheduled maintenance window. The most common use is **extending** an active window when a deploy runs longer than expected — call this with the new ``endsAt`` to keep alerts suppressed past the original deadline. The endpoint is a full replacement (PUT, not PATCH): pass the complete intended state, not a delta. Any field omitted falls back to the underlying model's default rather than preserving the existing value. Time fields use ISO 8601 / RFC 3339 timestamps with explicit timezone (UTC preferred), e.g. ``"2026-05-15T16:30:00Z"``. Body fields (same schema as create): - ``startsAt`` (required) - ``endsAt`` (required) - ``monitorId`` (optional; null = org-wide) - ``reason`` (optional; null clears) - ``repeatRule`` (optional; null clears the recurrence) - ``suppressAlerts`` (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| window_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_monitor Update Monitor ~30
Update an existing monitor's configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| monitor_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_notification_policy Update Notification Policy ~29
Update a notification policy.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| policy_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_resource_group Update Resource Group ~29
Update a resource group.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| group_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_secret Update Secret ~30
Update a secret's value by key.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_status_page Update Status Page ~41
Update a status page's name, slug, branding, visibility, or incident mode.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
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
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 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 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 4,733 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 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DevHelm MCP Server server under?
DevHelm MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the DevHelm MCP Server server?
VerifyMCP ran 16 checks on DevHelm MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.