Manage uptime monitors, incidents and status pages from any MCP client.
Inferred from the transports this listing declares (streamable-http). 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.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
list_workspacesList the workspaces and projects this connection can use, with their ids. Pass an id as `workspace` / `project` to any other tool to act there.List the workspaces and projects this connection can use, with their ids. Pass an id as `workspace` / `project` to any other tool to act there.
No input schema was published for this tool.
create_workspaceCreate a new workspace (with a first project) owned by the user. Only works when the user authorized access to all workspaces. Use the returned id as `workspace` in other tools.Create a new workspace (with a first project) owned by the user. Only works when the user authorized access to all workspaces. Use the returned id as `workspace` in other tools.
No input schema was published for this tool.
create_projectCreate a project in a workspace (pass `workspace`; omit for the default one). Only works where this connection has access to all projects of that workspace. The new project is usable straight away.Create a project in a workspace (pass `workspace`; omit for the default one). Only works where this connection has access to all projects of that workspace. The new project is usable straight away.
No input schema was published for this tool.
list_monitorsList the monitors of the current project with status, uptime and latency.List the monitors of the current project with status, uptime and latency.
No input schema was published for this tool.
get_monitorGet one monitor with its recent checks and uptime.Get one monitor with its recent checks and uptime.
No input schema was published for this tool.
create_monitorCreate a monitor. type is http, tcp, dns, heartbeat, postgres, mysql or redis; target is the URL, host:port or hostname. Omitted fields take defaults (60 s interval, expect HTTP 200). regions defaults to ["auto"]; name other regions (see list_regions) to check http and tcp monitors from several pla…Create a monitor. type is http, tcp, dns, heartbeat, postgres, mysql or redis; target is the URL, host:port or hostname. Omitted fields take defaults (60 s interval, expect HTTP 200). regions defaults to ["auto"]; name other regions (see list_regions) to check http and tcp monitors from several pla…
No input schema was published for this tool.
update_monitorChange fields of a monitor; only the named fields are modified. Set paused to pause or resume it.Change fields of a monitor; only the named fields are modified. Set paused to pause or resume it.
No input schema was published for this tool.
pause_monitorPause a monitor: no checks run and no alerts are sent until it is resumed.Pause a monitor: no checks run and no alerts are sent until it is resumed.
No input schema was published for this tool.
resume_monitorResume a paused monitor.Resume a paused monitor.
No input schema was published for this tool.
run_checkRun a check for a monitor right now and record the result. With `region` (an id from list_regions) it is one request from that region instead: the result is returned and nothing is recorded.Run a check for a monitor right now and record the result. With `region` (an id from list_regions) it is one request from that region instead: the result is returned and nothing is recorded.
No input schema was published for this tool.
list_regionsList the regions checks can run from on this deployment (`auto` is always there) and how many one monitor may use. Set a monitor's `regions` to use them.List the regions checks can run from on this deployment (`auto` is always there) and how many one monitor may use. Set a monitor's `regions` to use them.
No input schema was published for this tool.
delete_monitorprivilegedPermanently delete a monitor and its history.Permanently delete a monitor and its history.
No input schema was published for this tool.
list_incidentsList incidents (open ones first), automatic and manual.List incidents (open ones first), automatic and manual.
No input schema was published for this tool.
get_incidentGet an incident with its update timeline and the failed checks around it.Get an incident with its update timeline and the failed checks around it.
No input schema was published for this tool.
create_incidentOpen a manual incident, optionally tied to a monitor. Appears on status pages that include that monitor.Open a manual incident, optionally tied to a monitor. Appears on status pages that include that monitor.
No input schema was published for this tool.
post_incident_updatePost a status update on an incident. status resolved closes it. Subscribers and alert channels are notified.Post a status update on an incident. status resolved closes it. Subscribers and alert channels are notified.
No input schema was published for this tool.
acknowledge_incidentAcknowledge an incident as the API key's owner.Acknowledge an incident as the API key's owner.
No input schema was published for this tool.
list_status_pagesList the status pages of the current project.List the status pages of the current project.
No input schema was published for this tool.
create_status_pageCreate a public status page at /status/<slug> showing the given monitors (monitorIds). The slug is 3-40 lowercase letters, digits or hyphens and must be unused.Create a public status page at /status/<slug> showing the given monitors (monitorIds). The slug is 3-40 lowercase letters, digits or hyphens and must be unused.
No input schema was published for this tool.
update_status_pageChange a status page's title, theme, latency display or the monitors it shows (monitorIds replaces the list).Change a status page's title, theme, latency display or the monitors it shows (monitorIds replaces the list).
No input schema was published for this tool.
list_channelsList alert channels (email, webhook, Slack…) with their ids, to attach to monitors.List alert channels (email, webhook, Slack…) with their ids, to attach to monitors.
No input schema was published for this tool.
list_maintenanceList scheduled maintenance windows.List scheduled maintenance windows.
No input schema was published for this tool.
22 of 22 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Manage uptime monitors, incidents and status pages from any MCP client.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.