Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro 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.
Each card is one request a support team gets, and the Updown.io actions Ayro runs to close it.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Updown.io actions it has and picks the ones a request needs.
Authorize the Updown.io account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Updown.io actions that close it and chains as many as the request needs.
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 freeUpdown.io · Ayro
What can you do in Updown.io without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 5 actions your agent can call on Updown.io, straight from the live MCP connection.
Retrieve all monitoring checks on your updown.io account.
Retrieve a list of all updown.io server IP addresses.
List all updown.io server IPv4 addresses.
Retrieve a list of all updown.io server IPv6 addresses.
Retrieve a list of all updown.io monitoring servers.
Same connection, same setup. Pick the next one your team already uses.
Settles factual questions mid-conversation: airline and airport detail, city weather and air quality, currency conversion, age math, and word lookups.
Explains why a job failed, triggers a pipeline rerun, manages contexts and environment variables, and reports flaky tests and credit spend.
Reads repositories and tags, provisions repos and push webhooks, manages organization access, and removes stale tags and digests.
Checks domain availability and ownership, spins up free subdomains, manages VPS SSH keys, and reports on DNS, orders, and renewals.
Searches cached URLs, fetches prerendered snapshots, recaches pages after a deploy, schedules wildcard cache clears, and tracks the job.
Uploads files to IPFS, lists a project's smart contracts and templates, and reviews or removes the webhook watchers behind on-chain events.

Authorize the account and your agent has all 5 actions from the first conversation.
