Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.
Scored across 2 tools
The two tools have entirely distinct purposes: search_tools discovers available Uptimely tools, while execute_typescript runs code that invokes them. There is no functional overlap or plausible misselection between them.
Both names follow a strict verb_noun snake_case convention (search_tools, execute_typescript). The pattern is predictable and readable throughout.
Two tools is below the typical 3-15 range, but for a code-mode gateway that dynamically exposes arbitrary Uptimely tools, a search+execute pair is a reasonable minimal interface. It is slightly thin but each tool clearly earns its place.
The server's domain is dynamic tool orchestration, and the surface covers the full loop: discovery via search_tools and invocation via execute_typescript. No obvious discovery or execution gap remains.
Run a short TypeScript program that orchestrates Uptimely MCP tools (found via search_tools) in an isolated sandbox. See the server instructions for the full contract.
Inputs: code (required). Returns: logs, error, result, success
Find the Uptimely MCP tools this connection can reach, returned as TypeScript declarations to call from execute_typescript. See the server instructions for the full contract.
Inputs: query. Returns: count, declarations
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents
Uptime monitoring and public status page: HTTP monitors, down/up alerts and incidents.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Add one secure layer between your agents and this server.
