UptimeRobot logo

UptimeRobot + Memtro

Which monitors are down in UptimeRobot, what failed last week, and last month's uptime.

Connect UptimeRobot with an API key and Memtro reads monitors with URL, type, status and tags, incidents with cause, start, resolution and comments, uptime statistics for a period, maintenance windows, status pages and alert contacts. It reads on demand and there is no hourly sync. When you ask, with the main API key, and once an administrator has granted the action by name, it can comment on incidents, pause, resume, create or edit monitors, schedule maintenance, and post announcements to a public status page, which reach its subscribers. Deleting a monitor or resetting its statistics is permanent.

In Memtro

What you can do with UptimeRobot in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right UptimeRobot tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Monitors by status, name, URL fragment or tags, with type, check interval and current status
  2. 02Incidents by monitor, open status, type, cause and start date, covering downtime, slow responses and visual changes
  3. 03One incident with up to 20 of its comments, and uptime statistics across monitors for a day, week, month, year or all time
  4. 04Maintenance windows, public status pages with their monitors, and alert contacts by email, SMS or Slack
  5. 05When asked and granted, adds or edits internal incident comments, pauses, resumes, creates or edits monitors, including who is alerted, and schedules or deletes maintenance windows
  6. 06When asked and granted, posts, edits, publishes or archives a status page announcement, public and sent to subscribers once published, and permanently deletes a monitor or resets its statistics

Acts when asked

When you ask it to

These tools change something in UptimeRobot. 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.

  1. 01Add an internal comment to an incident
  2. 02Edit an internal incident comment
  3. 03Pause an UptimeRobot monitor
  4. 04Resume a paused UptimeRobot monitor
  5. 05Create an UptimeRobot monitor
  6. 06Edit an UptimeRobot monitor
  7. 07Delete an UptimeRobot monitor (permanent, with its history)
  8. 08Reset an UptimeRobot monitor's statistics (permanent)
  9. 09Schedule an UptimeRobot maintenance window
  10. 10Delete an UptimeRobot maintenance window
  11. 11Post an announcement on an UptimeRobot status page (public when published)
  12. 12Edit, publish or archive a status page announcement

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in UptimeRobot, choosing the same kinds; the tab shows UptimeRobot's own steps. Each event can start a job, with the event as its input. UptimeRobot sends a secret with every delivery, and one without it is refused.

Events and webhooks
  • 01A monitor went down
  • 02A monitor came back up
  • 03An SSL certificate or domain is about to expire
In practice

Ask it like you would a colleague

Once UptimeRobot 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.

UptimeRobot logoUptimeRobot + Memtro
  • Which monitors are down right now?

  • When was the website last down, and for how long?

  • What was our uptime last month across all monitors?

  • Pause the staging monitor until Monday

  • Schedule a maintenance window for the API monitors tonight from 22:00 to 23:00

01

Monthly uptime figure

The founder wants an uptime figure for the board pack. Memtro reads UptimeRobot's statistics for the last month across monitors, then the incidents in that period with cause, start and resolution, and gives the uptime with each outage that dented it.

02

Planned database upgrade

Before Saturday's database upgrade, engineer Nadia Petrova asks Memtro to quiet the alerts and warn customers. Memtro schedules a maintenance window for the API monitors and, with the wording she approved, publishes an announcement on the Acme status page, which goes to its subscribers.

Teams

Where it fits

The teams that lean on UptimeRobot most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in UptimeRobot 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.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    In the UptimeRobot dashboard → Integrations → API, create a read-only API key if Memtro should only read, or use the main API key, which every change (monitors, maintenance windows, announcements, comments) needs

  2. 2

    Copy the key

  3. 3

    In Memtro open Connections → UptimeRobot, paste the API key and connect

  4. 4

    Ask which monitors are down. The free plan allows 10 API requests a minute, paid plans twice the monitor count

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The UptimeRobot tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in UptimeRobot?+

Only when you ask, and only what it has been granted: add an internal comment to an incident; edit an internal incident comment; pause an UptimeRobot monitor; resume a paused UptimeRobot monitor; create an UptimeRobot monitor; edit an UptimeRobot monitor; delete an UptimeRobot monitor (permanent, with its history); reset an UptimeRobot monitor's statistics (permanent); schedule an UptimeRobot maintenance window; delete an UptimeRobot maintenance window; post an announcement on an UptimeRobot status page (public when published); edit, publish or archive a status page announcement. 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.

Who can use a UptimeRobot connection?+

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.

Does Memtro store my UptimeRobot data?+

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.

How do I connect UptimeRobot?+

API key. In the UptimeRobot dashboard → Integrations → API, create a read-only API key if Memtro should only read, or use the main API key, which every change (monitors, maintenance windows, announcements, comments) needs.

Can UptimeRobot start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in UptimeRobot, choosing the same kinds; the tab shows UptimeRobot'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.

Connect UptimeRobot in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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