A
licenseA
qualityB
maintenanceMCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
22
57
2
MIT
DevHelm MCP Server
Officialby devhelmhq
Related Servers
Alternatives to DevHelm MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for StillOnline uptime monitoring, enabling management of projects, checks, incidents, and public status pages through natural language.10231MIT
- AlicenseAqualityCmaintenanceMCP server for CronAlert uptime monitoring — manage monitors, check results, and incidents from any MCP-compatible AI client.962MIT
- AlicenseAqualityBmaintenanceMonitor MCP server health, uptime, response times, and Azure DevOps pipeline status14121MIT
uptrack-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.12MIT- FlicenseNot gradedqualityDmaintenanceMonitors MCP server uptime, auth failures, schema drift, and SLA evidence.-
TDQS
C2.9/5.0
Scored across 129 tools
Disambiguation4/5
Tools are generally clearly distinct by resource type, and descriptions explicitly differentiate similar concepts like service incidents, workspace incidents, and status page incidents. However, the sheer volume and several near-synonyms (e.g., get_service_uptime vs get_component_uptime, create_maintenance_window vs create_status_page_maintenance) could still cause occasional misselection.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (list_, get_, create_, update_, delete_, etc.) with clear resource prefixes like service, monitor, incident, status_page, and maintenance_window. Even oddities like acquire_deploy_lock or reorder_status_page_layout still start with strong action verbs, and there is no mixing of naming conventions.
Tool Count1/5
129 tools is far beyond the extreme threshold for a coherent MCP tool surface. While each tool may be individually useful, the count makes the server unwieldy and closer to a full admin API than a curated agent toolset.
Completeness4/5
The server covers an exceptionally broad domain with CRUD operations for monitors, incidents, status pages, maintenance windows, alert channels, webhooks, API keys, secrets, tags, environments, resource groups, and dependencies. Minor gaps exist, such as no update or delete operation for workspace incidents and no unrevoke for API keys, but these are edge cases.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive