UptimeRobot
Manage monitors and alert contacts, and check account status, via the UptimeRobot API v2.
About
UptimeRobot ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.uptimerobot- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Monitoring & Observability
Overview
UptimeRobot monitors websites, servers, and other endpoints for downtime, and this app manages the monitors and alert contacts behind an account: listing and creating monitors, updating what they check and how often, resetting a monitor’s uptime statistics, and reading the alert contacts notified when something goes down. It is built for workflows that provision or maintain monitoring as part of a larger process — standing up a monitor when a new service goes live, or auditing what is currently being watched.
Account-level details are also readable directly, useful for checking plan limits and usage before creating another monitor. Monitors can be deleted once no longer needed, and every write against the API is handled the same way UptimeRobot expects: as a single account-wide credential rather than anything scoped per monitor, so a workflow’s connection can manage everything on the account it is authorized for.
Build with UptimeRobot
Three routes to the same 8 actions. The Workflow tab is generated from UptimeRobot's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Account Details
account-get Get the connected account's monitor limit, interval, and monitor counts.
List Monitors
monitor-list List monitors in the account, optionally filtered by status, type, or search.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying UptimeRobot's real ids.
{
"manifestVersion": "2",
"name": "uptimerobot-example",
"steps": [
{
"id": "monitor-create",
"uses": {
"app": "io.w6w.uptimerobot",
"action": "monitor-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"friendlyName": "<friendlyName>",
"url": "<url>",
"type": "<type>"
}
}
]
}Here are some of the things you can do
-
Create Monitor
performmonitor-create -
Get Account Details
readaccount-get -
List Alert Contacts
readalert-contact-list -
Get Monitor
readmonitor-get -
List Monitors
readmonitor-list
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for UptimeRobot, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to UptimeRobot. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "monitor-create",
payload: {
friendlyName: "<value>",
url: "<value>",
type: "<value>",
// subType: "<value>",
// port: "<value>",
// keywordType: "<value>",
// keywordValue: "<value>",
// interval: "<value>",
// timeout: "<value>",
// httpUsername: "<value>",
// httpPassword: "<value>",
// httpAuthType: "<value>",
// alertContacts: "<value>",
// ignoreSslErrors: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action monitor-create --payload '{"friendlyName":"<value>","url":"<value>","type":"<value>"}'Give an AI agent UptimeRobot — without giving it UptimeRobot's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.uptimerobot#monitor-create",
"input": {
"friendlyName": "<friendlyName>",
"url": "<url>",
"type": "<type>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's UptimeRobot connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
UptimeRobot's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. UptimeRobot itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
UptimeRobot declares its own checks, so its health is a property of the app rather than something the host guesses at.
UptimeRobot platform status
API rate limit headroom
Reads UptimeRobot's X-RateLimit-* response headers off a getAccountDetails call.