Devhelm MCP Server
devhelm-mcp-server
PyPI
v1.4.0
Published by devhelmhq — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: get_policy_snapshot → get_environment → create_webhook. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow get_policy_snapshot → get_environment → create_webhook
Tools 121
Each tool and what it can reach — statically extracted from the published source.
create_webhooknetwork egressdelete_webhooknetwork egressget_environmentreads sensitive dataget_policy_snapshotingests untrusted inputlist_secretsreads sensitive datatest_webhooknetwork egressupdate_webhooknetwork egressacquire_deploy_lockno sensitive capabilityadd_resource_group_memberno sensitive capabilityadd_status_page_domainno sensitive capability
Show 111 more tools ↓
add_status_page_subscriberno sensitive capabilitycancel_maintenance_windowno sensitive capabilitycreate_alert_channelno sensitive capabilitycreate_api_keyno sensitive capabilitycreate_environmentno sensitive capabilitycreate_incidentno sensitive capabilitycreate_maintenance_windowno sensitive capabilitycreate_monitorno sensitive capabilitycreate_notification_policyno sensitive capabilitycreate_resource_groupno sensitive capabilitycreate_secretno sensitive capabilitycreate_status_pageno sensitive capabilitycreate_status_page_componentno sensitive capabilitycreate_status_page_groupno sensitive capabilitycreate_status_page_incidentno sensitive capabilitycreate_tagno sensitive capabilitydelete_alert_channelno sensitive capabilitydelete_api_keyno sensitive capabilitydelete_dependencyno sensitive capabilitydelete_environmentno sensitive capabilitydelete_monitorno sensitive capabilitydelete_notification_policyno sensitive capabilitydelete_resource_groupno sensitive capabilitydelete_secretno sensitive capabilitydelete_status_pageno sensitive capabilitydelete_status_page_componentno sensitive capabilitydelete_status_page_groupno sensitive capabilitydelete_status_page_incidentno sensitive capabilitydelete_tagno sensitive capabilitydismiss_status_page_incidentno sensitive capabilityforce_release_deploy_lockno sensitive capabilityget_alert_channelno sensitive capabilityget_all_components_uptimeno sensitive capabilityget_api_keyno sensitive capabilityget_check_traceno sensitive capabilityget_component_uptimeno sensitive capabilityget_current_deploy_lockno sensitive capabilityget_dependencyno sensitive capabilityget_incidentno sensitive capabilityget_incident_timelineno sensitive capabilityget_maintenance_windowno sensitive capabilityget_monitorno sensitive capabilityget_notification_policyno sensitive capabilityget_resource_groupno sensitive capabilityget_serviceno sensitive capabilityget_service_day_rollupno sensitive capabilityget_service_incidentno sensitive capabilityget_service_live_statusno sensitive capabilityget_service_uptimeno sensitive capabilityget_services_summaryno sensitive capabilityget_status_overviewno sensitive capabilityget_status_pageno sensitive capabilityget_status_page_incidentno sensitive capabilityget_tagno sensitive capabilityget_webhookno sensitive capabilitylist_alert_channelsno sensitive capabilitylist_api_keysno sensitive capabilitylist_dependenciesno sensitive capabilitylist_environmentsno sensitive capabilitylist_incidentsno sensitive capabilitylist_maintenance_windowsno sensitive capabilitylist_monitor_resultsno sensitive capabilitylist_monitor_rule_evaluationsno sensitive capabilitylist_monitor_transitionsno sensitive capabilitylist_monitor_versionsno sensitive capabilitylist_monitorsno sensitive capabilitylist_notification_policiesno sensitive capabilitylist_resource_groupsno sensitive capabilitylist_service_categoriesno sensitive capabilitylist_service_componentsno sensitive capabilitylist_service_incidentsno sensitive capabilitylist_service_maintenancesno sensitive capabilitylist_status_page_componentsno sensitive capabilitylist_status_page_domainsno sensitive capabilitylist_status_page_groupsno sensitive capabilitylist_status_page_incidentsno sensitive capabilitylist_status_page_subscribersno sensitive capabilitylist_status_pagesno sensitive capabilitylist_tagsno sensitive capabilitylist_webhooksno sensitive capabilitypause_monitorno sensitive capabilitypost_status_page_incident_updateno sensitive capabilitypublish_status_page_incidentno sensitive capabilityrelease_deploy_lockno sensitive capabilityremove_resource_group_memberno sensitive capabilityremove_status_page_domainno sensitive capabilityremove_status_page_subscriberno sensitive capabilityreorder_status_page_componentsno sensitive capabilityreorder_status_page_layoutno sensitive capabilityresolve_incidentno sensitive capabilityresume_monitorno sensitive capabilityrevoke_api_keyno sensitive capabilitysearch_servicesno sensitive capabilitytest_alert_channelno sensitive capabilitytest_monitorno sensitive capabilitytest_notification_policyno sensitive capabilitytrack_dependencyno sensitive capabilityupdate_alert_channelno sensitive capabilityupdate_dependency_alert_sensitivityno sensitive capabilityupdate_environmentno sensitive capabilityupdate_maintenance_windowno sensitive capabilityupdate_monitorno sensitive capabilityupdate_notification_policyno sensitive capabilityupdate_resource_groupno sensitive capabilityupdate_secretno sensitive capabilityupdate_status_pageno sensitive capabilityupdate_status_page_componentno sensitive capabilityupdate_status_page_groupno sensitive capabilityupdate_status_page_incidentno sensitive capabilityupdate_tagno sensitive capabilityverify_status_page_domainno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (121 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.4.0 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan devhelm-mcp-server --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.