Can Lyro add a check or change a monitoring setting?

No. All five actions in this toolkit are reads - the checks list plus the node and IP listings. List All Checks shows each check's settings, but changing an interval, adding a URL or editing an alert rule stays inside updown.io.

Why would Lyro fetch updown.io's IP addresses?

Because a firewall or WAF that blocks the monitoring nodes reports as downtime that never happened. The node lists give the current IPv4 and IPv6 addresses to allowlist, and they are worth re-checking rather than trusting a list pasted into a ticket a year ago.

Does Lyro alert the team when a check goes down?

No - updown.io sends its own alerts and this toolkit exposes no alert, webhook or subscription action. Lyro answers on request, reading the current state of a check when someone asks, rather than pushing a notification of its own.

Which checks can Lyro see?

Only those belonging to the updown.io account whose API key is connected. There is no cross-account listing here, so a check configured under a different account or team is invisible to Lyro until that account is connected too.

Updown.io MCP integration

Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.

Connect Updown.io See all integrations

5actions available

What your agent can do with Updown.io

Every action runs live through MCP. Nothing to build, nothing to maintain.

List all checks
Lyro displays all active uptime monitoring checks to show which services are being watched. Support teams identify monitoring gaps immediately instead of asking engineers to review setup.

See all 5 actions

How businesses use Updown.io + Lyro

Each card is one request a support team gets, and the Updown.io actions Lyro runs to close it.

Confirm what is monitored and from where
Lyro lists every check on the account with its status, uptime and settings, and the monitoring nodes those checks run from, so a URL nobody added is spotted before an outage makes the gap obvious.
List All ChecksList Monitoring Nodes
Hand over the allowlist a firewall needs
Lyro returns the current updown.io node addresses, in the IPv4 or IPv6 set the firewall in question expects, so monitoring traffic is allowed through instead of being blocked and read as downtime.
List Node IPsList node IPv4 addressesList IPv6 nodes

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Updown.io actions it has and picks the ones a request needs.

01
Connect Updown.io
Authorize the Updown.io account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Updown.io actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Updown.io · Lyro

Everything else about Updown.io

Setup, permissions, and the limits of what Lyro can do inside Updown.io.

No. All five actions in this toolkit are reads - the checks list plus the node and IP listings. List All Checks shows each check's settings, but changing an interval, adding a URL or editing an alert rule stays inside updown.io.