Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
Model Context Protocol (MCP) server for DevHelm — gives AI coding assistants (Cursor, Claude Desktop, Windsurf, etc.) access to your uptime monitors, incidents, alerting, and more. Use the hosted server at . Two connection modes: API key in URL (for clients that only accept a URL): Or with (no install required): Add to your MCP config: Monitors | list, get, create, update, delete, pause, resume,…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Model Context Protocol (MCP) server for DevHelm — gives AI coding assistants (Cursor, Claude Desktop, Windsurf, etc.) access to your uptime monitors, incidents, alerting, and more. Use the hosted server at . Two connection modes: API key in URL (for clients that only accept a URL): Or with (no install required): Add to your MCP config: Monitors | list, get, create, update, delete, pause, resume, test, results, versions | Incidents | list, get, create, resolve, delete | Alert Channels | list,…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.