Checkly
Run and inspect Checkly synthetic monitors, their results, alerts and maintenance windows.
About
Checkly ships in the w6w first-party pack. It declares 25 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.checkly- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Monitoring & Observability · DevOps & Infrastructure · Developer Tools
Overview
Checkly runs synthetic monitors — scripted checks that hit an API or browse a page on a schedule — and this app puts the results of that monitoring into a workflow. List and inspect checks and the groups they belong to, trigger an ad-hoc run, and read back results, current status and the alerts Checkly actually sent.
Beyond the read path, it can activate, deactivate or mute a check, open and close maintenance windows to silence monitoring during a planned deploy, and manage the environment variables a check’s script depends on. Reporting and account-entitlement actions round out the picture for a workflow that needs to know what the current plan allows.
The distinctions matter here: a muted check keeps recording without paging anyone, a deactivated one stops recording entirely, and a triggered run reports only that it started, not whether it passed. This app surfaces those states the way Checkly itself defines them rather than collapsing everything into a single pass-or-fail signal.
Build with Checkly
Three routes to the same 25 actions. The Workflow tab is generated from Checkly'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 plan entitlements
account-entitlements-get What this account's plan allows — the maximums, not the usage.
Get an alert channel
alert-channel-get One alert channel, including which event kinds it actually sends.
List alerts sent
check-alert-list The alerts Checkly actually sent — not the same as the failures recorded.
List a group's checks
check-group-checks-list The checks in a group, with the group's settings applied.
List check groups
check-group-list List check groups, which share settings and alerting across their checks.
Get a check result
check-result-get The full record of one run, with its response or console output.
List a check's results
check-result-list The run history of one monitor, optionally only the failures.
List current check statuses
check-status-list The current pass/fail state of every check, in one call.
Activate, deactivate or mute a check
check-toggle Turn a monitor on or off, or silence its alerts while it keeps running.
Create a maintenance window
maintenance-window-create Silence (or pause) monitoring for a bounded period — the deploy-window action.
Delete a maintenance window
maintenance-window-delete End a maintenance window, restoring alerting immediately.
List maintenance windows
maintenance-window-list List maintenance windows — the usual reason alerts have gone quiet.
Get an availability report
reporting-get Aggregated success rate and response times per check over a window.
Delete an environment variable
variable-delete Delete a variable. Checks that read it may keep passing while testing nothing.
Set an environment variable
variable-set Create or update a variable checks can read. Secret values cannot be read back.
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 Checkly's real ids.
{
"manifestVersion": "2",
"name": "checkly-example",
"steps": [
{
"id": "alert-channel-get",
"uses": {
"app": "io.w6w.checkly",
"action": "alert-channel-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"channelId": "<channelId>"
}
}
]
}Here are some of the things you can do
-
Get an alert channel
readalert-channel-get -
Get plan entitlements
readaccount-entitlements-get -
List alert channels
readalert-channel-list -
List alerts sent
readcheck-alert-list -
Get a check
readcheck-get
+20 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 Checkly, 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 Checkly. 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: "alert-channel-get",
payload: {
channelId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action alert-channel-get --payload '{"channelId":"<value>"}'Give an AI agent Checkly — without giving it Checkly'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.checkly#alert-channel-get",
"input": {
"channelId": "<channelId>"
}
}
}
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 Checkly 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
Checkly'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. Checkly itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Checkly declares its own checks, so its health is a property of the app rather than something the host guesses at.