Can Lyro create, edit, or pause a Pingdom check?

No. The connected toolkit is read and test only - it lists uptime and transaction checks, alert actions, contacts, teams, and maintenance windows, and Get Single Check runs a one-off test that is never saved. Creating, editing, or pausing a check stays in Pingdom.

Can Lyro tell us which IP addresses to allowlist for Pingdom?

Yes. Get Probes returns every probe server worldwide with its IPv4 and IPv6 addresses, country, region, and availability status, so Lyro can produce the allowlist for the specific locations your checks run from rather than a blanket range.

How does Lyro know whether we can add another check?

Get Credits returns account-level capacity: uptime and transaction check limits, SMS credits, RUM sites, and alerting user slots, each with the current count against what is available. Lyro reads that before suggesting another check, so the answer reflects the plan you are actually on.

Does the on-demand test Lyro runs affect our monitoring history?

No. Get Single Check executes one immediate test against a target host from a chosen or random probe and returns that result. It is not one of the configured checks, so it does not appear in the checks list or become part of the history those checks build up.

Pingdom MCP integration

Lists uptime and transaction checks, traces which alert reached which contact, and runs an on-demand test from a chosen global probe.

Connect Pingdom See all integrations

13actions available

Three actions you can hand over today

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

Get single check
Lyro runs an on-demand check against a target host to verify its current status. Support agents can instantly confirm whether a service is up or down.
Get checks list
Lyro retrieves all uptime monitoring checks configured in Pingdom. Agents see the complete monitoring landscape to explain coverage gaps to customers.
List maintenance occurrences
Lyro retrieves the history of completed maintenance windows from Pingdom. Agents can reference past downtime to explain service interruptions to customers.

See all 13 actions

How businesses use Pingdom + Lyro

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

Report the current state of every monitoring check
Lyro lists the uptime checks with their status, type, and tags, pulls the transaction checks alongside them, and reports how many check slots and SMS credits the account still has available.
Get Checks ListGet TMS Transaction Checks ListGet Credits
Trace who was alerted and how
Lyro reads the alert actions fired for a check, then opens the contact behind them to show the email and SMS targets configured, the teams that contact belongs to, and whether it is currently paused.
Get Pingdom Alert ActionsGet Contact DetailsGet Teams
Check whether an outage is planned maintenance
Before a failing check is treated as an incident, Lyro looks up the maintenance windows on the account and the occurrences that fall inside the time range in question.
Get Maintenance WindowsList Maintenance Occurrences
Test a host from the region a customer reports from
Lyro picks a probe in the right country from Pingdom's worldwide list and executes an immediate check against the host, so a report that the site is slow in one region is verified rather than assumed.
Get Single CheckGet ProbesGet Reference Data

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 Pingdom actions it has and picks the ones a request needs.

01
Connect Pingdom
Authorize the Pingdom 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 Pingdom 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

Pingdom · Lyro

Everything else about Pingdom

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

No. The connected toolkit is read and test only - it lists uptime and transaction checks, alert actions, contacts, teams, and maintenance windows, and Get Single Check runs a one-off test that is never saved. Creating, editing, or pausing a check stays in Pingdom.

Every action available in Pingdom

All 13 actions your agent can call on Pingdom, straight from the live MCP connection.

Get pingdom alert actions
Retrieves configured alert actions (notifications) from your Pingdom account.
Get checks list
Retrieves a list of all uptime/monitoring checks configured in Pingdom with optional filtering and pagination.
Get contact details
Retrieves comprehensive details of a specific Pingdom alerting contact by ID, including all configured notification methods (email, SMS), team memberships, contact type, and pause status.
Get contacts
Retrieve all alerting contacts.
Get credits
Retrieves comprehensive account information including check limits, SMS credits, and resource usage.
List maintenance occurrences
List maintenance occurrences.
Get maintenance windows
Retrieve a list of maintenance windows.
Get probes
Retrieves the complete list of Pingdom probe servers worldwide.
Get reference data
Retrieves Pingdom reference data including regions, timezones, datetime formats, number formats, and countries.
Get single check
Perform a single on-demand Pingdom check against a target host.
Get team details
Fetch detailed information for a specific alerting team.
Get teams
Retrieve all alerting teams and their members.
Get tms transaction checks list
Retrieves a paginated list of all transaction (TMS) checks configured in Pingdom.