StatusCake integration for AI agents.
StatusCake integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves StatusCake tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real StatusCake actions, managed and audited.
Your user connects StatusCake once; your agent can then website Monitoring solution that drives revenue & keeps you online. Track your uptime, page speed, domain, server, & SSL certificates — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants StatusCake access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported StatusCake tools.
36 tools are generated from the published StatusCake catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 36 tools. All published catalog entries are included in this page's server-rendered HTML.
- Create a contact group
- Creates a contact group with the given parameters.
- contact groups
- Create a heartbeat check
- Creates a heartbeat check with the given parameters.
- heartbeat
- Create a maintenance window
- Creates a maintenance window with the given parameters.
- maintenance windows
- Create a pagespeed check
- Creates a pagespeed check with the given parameters.
- pagespeed
- Create an SSL check
- Creates an SSL check with the given parameters.
- ssl
- Create an uptime check
- Creates an uptime check with the given parameters.
- uptime
- Delete a contact group
- Deletes a contact group with the given id.
- contact groups
- Delete a heartbeat check
- Deletes a heartbeat check with the given id.
- heartbeat
- Delete a maintenance window
- Deletes a maintenance window with the given id.
- maintenance windows
- Delete a pagespeed check
- Deletes a pagespeed check with the given id.
- pagespeed
- Delete an SSL check
- Deletes an SSL check with the given id.
- ssl
- Delete an uptime check
- Deletes an uptime check with the given id.
- uptime
- Retrieve a contact group
- Returns a contact group with the given id.
- contact groups
- Retrieve a heartbeat check
- Returns a heartbeat check with the given id.
- heartbeat
- Retrieve a maintenance window
- Returns a maintenance window with the given id.
- maintenance windows
- Retrieve a pagespeed check
- Returns a pagespeed check with the given id.
- pagespeed
- Retrieve an SSL check
- Returns an SSL check with the given id.
- ssl
- Retrieve an uptime check
- Returns an uptime check with the given id.
- uptime
- Get all contact groups
- Returns a list of contact groups for an account.
- contact groups
- Get all heartbeat checks
- Returns a list of heartbeat checks for an account.
- heartbeat
- Get all maintenance windows
- Returns a list of maintenance windows for an account.
- maintenance windows
- Get all pagespeed monitoring locations
- Returns a list of locations detailing server information for pagespeed monitoring servers. This information can be used to create further checks using the API.
- locations
- Get all pagespeed check history
- Returns a list of pagespeed check history results for a given id, detailing the runs performed on the StatusCake testing infrastruture. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`. Aggregated data over the specified duration is returned in the root level `metadata` field.
- pagespeed
- Get all pagespeed checks
- Returns a list of pagespeed checks for an account.
- pagespeed
- Get all SSL checks
- Returns a list of SSL checks for an account.
- ssl
- Get all uptime monitoring locations
- Returns a list of locations detailing server information for uptime monitoring servers. This information can be used to create further checks using the API.
- locations
- Get all uptime check alerts
- Returns a list of uptime check alerts for a given id. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.
- uptime
- Get all uptime check history
- Returns a list of uptime check history results for a given id, detailing the runs performed on the StatusCake testing infrastruture. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.
- uptime
- Get all uptime check periods
- Returns a list of uptime check periods for a given id, detailing the creation time of the period, when it ended and the duration. The returned results are a paginated series. Alongside the response data is a `links` object referencing the current response document, `self`, and the next page in the series, `next`.
- uptime
- Get all uptime checks
- Returns a list of uptime checks for an account.
- uptime
- Update a contact group
- Updates a contact group with the given parameters.
- contact groups
- Update a heartbeat check
- Updates a heartbeat check with the given parameters.
- heartbeat
- Update a maintenance window
- Updates a maintenance window with the given parameters.
- maintenance windows
- Update a pagespeed check
- Updates a pagespeed check with the given parameters.
- pagespeed
- Update an SSL check
- Updates an SSL check with the given parameters.
- ssl
- Update an uptime check
- Updates an uptime check with the given parameters.
- uptime
StatusCake integration, answered
- How do AI agents use StatusCake through Open Connector?
- Your user connects StatusCake once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes StatusCake tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a StatusCake MCP server?
- Yes. Open Connector can serve StatusCake as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call StatusCake actions with credentials injected server-side.
- Where do StatusCake credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents StatusCake — keep the keys.
Open source, self-hostable, with StatusCake credentials that never leave your infrastructure. Run it from source today.