Ask when the website was last down, and which SSL certificates are close to expiry.
Connect StatusCake with an API token and Memtro reads uptime checks with their down periods and alerts sent, SSL certificate checks with expiry, heartbeat checks, page-speed checks and maintenance windows. Heartbeat push URLs are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create uptime, SSL and heartbeat checks, which count against the plan's quota, pause or change checks, permanently delete a check with its history, and create, change or delete maintenance windows, which silence alerts for the checks they cover.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right StatusCake tool, reads what it needs, and answers with the source cited.
These tools change something in StatusCake. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in StatusCake, choosing the same kinds; the tab shows StatusCake's own steps. Each event can start a job, with the event as its input. StatusCake sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce StatusCake is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
StatusCake + MemtroWhen was the website last down, and for how long?
Which uptime checks are down right now?
Which SSL certificates expire in the next 30 days?
Did the nightly backup heartbeat check in last night?
Set a maintenance window for the API checks on Saturday from 22:00 to 23:00
A customer at Brightwave Ltd says the site was down on Tuesday morning. Support asks Memtro, which reads the uptime check's history and finds one down period from 09:12 to 09:19, with the alerts StatusCake sent and the status codes returned.
Dan Fletcher asks Memtro to silence the Acme API alerts during Saturday's release. Memtro creates a maintenance window from 22:00 to 23:00 London time covering every check tagged api, so StatusCake sends no alerts for them while it runs.
The teams that lean on StatusCake most, a question each of them asks, and what they connect beside it.
A record in StatusCake is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn StatusCake open the Account panel → API tokens and create or copy a token. It reads and writes the whole account, as StatusCake has no read-only scopes
Without a subscription StatusCake allows 60 requests a minute, shared by everything using the account's token
Paste the API token into Connections → StatusCake in Memtro and connect
Ask when the website was last down
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The StatusCake tools are the same everywhere.
Only when you ask, and only what it has been granted: create an uptime check (counts against the plan's check quota; its contact groups are alerted when it fails); change an uptime check's settings, or pause or resume it; delete an uptime check and its history (permanent); create a maintenance window (silences alerts for the checks it covers); change a maintenance window; delete a maintenance window (permanent); create a heartbeat check (its push URL is not returned); create an SSL certificate check. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API token. In StatusCake open the Account panel → API tokens and create or copy a token. It reads and writes the whole account, as StatusCake has no read-only scopes.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in StatusCake, choosing the same kinds; the tab shows StatusCake's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
