Pingdom
Pingdom is a web performance monitoring service that allows users to monitor the uptime and performance of websites, servers, and applications.
Verdict
Common use cases
- Pull downtime alerts during incident triage
- Confirm check status before deploying
- Audit contact notification settings
- Review maintenance windows for the week
- Correlate probe failures with regional outages
Integration
- Vendor
- Pingdom
- Category
- other
- Auth
- API_KEY
- Tools
- 13
- Composio slug
pingdom
Tools
- Get Checks List
Tool to retrieve an overview list of all uptime checks with optional filters and pagination. use when you need to fetch checks after configuring probes or tags.
- Get Contact Details
Tool to fetch detailed info of a specific pingdom alerting contact. use when you need full configuration of a contact’s notification methods by contact id.
- Get Contacts
Tool to retrieve all alerting contacts. use when you need to list every contact along with their notification targets after establishing a pingdom session.
- Get Credits
Tool to retrieve account credit and rate-limit information. use when you need to check remaining checks and api credits before proceeding with further requests.
- Get Maintenance Windows
Tool to retrieve a list of maintenance windows. use when you need to list user's maintenance windows with optional pagination and time range filters.
- Get Pingdom Alert Actions
Tool to retrieve a list of alert actions for your pingdom account. use when you need to fetch actions with optional filters: pagination, check ids, user ids, status, via channel, or time range.
- Get Probes
Tool to retrieve all pingdom probe servers. use when you need to list available probes for uptime or transaction checks.
- Get Reference Data
Tool to retrieve pingdom reference data including time zones, states, probes, actions, roles, contact types, and integration types. use when you need account-wide reference lists before configuring checks.
- Get Single Check
Tool to perform a single pingdom check. use when you need an immediate test of a host or url from specific probes. example: "perform single check on example.com with http type".
- Get Team Details
Tool to fetch detailed information for a specific alerting team. use after listing teams to get full members and integrations details.
- Get Teams
Tool to retrieve all alerting teams and their members. use after authenticating to pingdom to manage team configurations.
- Get TMS Transaction Checks List
Tool to list all transaction (tms) checks. use when you need an overview of all scripted or recorded checks.
- List Maintenance Occurrences
Tool to list maintenance occurrences. use when you need occurrences filtered by time range or a specific maintenance window id.
Setup
Setup guide
- 11. In Switchy, open the Space where you want Pingdom available and click Integrations in the sidebar. 2. Search for Pingdom and click Connect. 3. You'll be prompted for a Pingdom API key — generate one in your Pingdom account under Settings > API Keys with at least read scope for checks, contacts, and alerts. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection by fetching your account credits. 6. Test it: in the Space chat, type '@Pingdom list all uptime checks' and send. 7. Pingdom returns a table of check names, statuses, and last response times. 8. If you see 'unauthorized', verify the API key has the correct scopes and hasn't expired.
What teammates see: by default, memories from Pingdom are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Active Checks
@Pingdom show me all uptime checks, including their current status and the last time each one responded.Open in a Space →
Recent Alert History
@Pingdom get all alert actions from the last 24 hours, filtered by status and sorted by timestamp.Open in a Space →
Check Maintenance Windows
@Pingdom retrieve all maintenance windows for the next seven days, including start and end times.Open in a Space →
Audit Contact Configuration
@Pingdom list all contacts with their email, SMS, and webhook targets so I can verify our on-call roster.Open in a Space →
Probe Server Inventory
@Pingdom show me all probe servers, grouped by region, so I can choose locations for a new uptime check.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Pingdom show me all uptime checks that are currently down or have triggered alerts in the last 24 hours
Based on your Pingdom account, 3 checks are currently reporting issues: 'API Gateway' (down for 12 minutes, last checked 2 minutes ago), 'Payment Processor' (slow response time averaging 4.2s, threshold 2s), and 'Admin Dashboard' (SSL certificate expires in 6 days). All other 47 monitored endpoints are responding normally. The API Gateway outage began at 14:23 UTC and has triggered notifications to your on-call Slack channel.
This example combines the Get Checks List tool with alert filtering to surface actionable monitoring data. Requires read access to checks and alert history. The MCP returns structured data about check status, response times, and recent incidents—useful for incident triage or daily standups.
@Pingdom create a 4-hour maintenance window starting now for all checks tagged 'database-migration' so we don't get false alerts during the upgrade
Maintenance window created successfully. Suppressing alerts for 6 checks tagged 'database-migration' from 15:00 UTC to 19:00 UTC today. Affected checks: PostgreSQL Primary, PostgreSQL Replica 1, PostgreSQL Replica 2, Redis Cache, Background Job Queue, and Data Warehouse API. During this window, downtime and performance degradation will not trigger notifications to your contacts or integrations.
Demonstrates the MCP's ability to modify monitoring state, not just read it. This write operation requires API credentials with maintenance-window permissions. Be aware that creating windows suppresses real alerts—confirm the time range and affected checks before execution to avoid missing genuine incidents outside the maintenance scope.
@Pingdom analyze our probe server distribution and recommend whether we should add coverage in Asia-Pacific based on our current check locations and response times
Your account uses 12 probe locations: 7 in North America, 4 in Europe, 1 in South America. Zero probes in Asia-Pacific. Reviewing your 52 checks, 8 target services with '.com.au' or '.co.nz' domains, currently monitored only from US-West and EU-Central probes. Average response time from these distant probes: 890ms. Adding Sydney or Tokyo probes would likely reveal sub-200ms response times for APAC users and provide more accurate uptime data for that region. Pingdom offers probes in Sydney, Tokyo, Singapore, and Mumbai.
This synthesis example pairs Pingdom's Get Probes and Get Checks List tools with the AI's reasoning to provide strategic monitoring advice. The MCP supplies raw probe and check data; the AI interprets geographic gaps and latency patterns. Useful for infrastructure planning, though recommendations depend on the AI accurately parsing domain hints and probe coordinates.
Use-case deep-dives
When Pingdom MCP speeds up root-cause analysis after downtime
A 6-person DevOps team runs a multi-region SaaS and needs to write incident reports within 2 hours of an outage. The Pingdom MCP pulls check history, alert actions, and maintenance windows into the AI workspace so the on-call engineer can correlate timeline events without switching tabs. This works when your postmortem template is consistent and you have fewer than 50 active checks—beyond that threshold, filtering the checks list becomes manual work the MCP can't optimize. The MCP also surfaces which contacts were notified and when, saving 15 minutes of Slack archaeology. If your team writes one postmortem a month or more, the time savings justify adding this integration to your Switchy workspace.
Why support reps use this MCP to answer 'is it down' tickets
A 3-person support team at a B2B platform fields 20-30 tickets a week asking if a specific endpoint is slow or offline. The Pingdom MCP lets the AI pull current check status and recent alert history in one query, so the rep can reply with actual uptime data instead of guessing or escalating to engineering. This scenario only works if your checks are named clearly enough that the MCP can match a customer's description to the right check—vague names like 'prod-api-1' break the workflow. The MCP also retrieves probe location data, which helps when a customer reports regional latency. If your support team spends more than 2 hours a week triaging uptime questions, this integration pays for itself by keeping tickets out of the engineering queue.
When this MCP replaces manual uptime reporting in standups
A 5-person platform team spread across 3 time zones runs a weekly async ops review where each engineer summarizes their service's uptime and alert volume. The Pingdom MCP generates those summaries automatically by querying checks, alert actions, and maintenance windows for the past 7 days, then formatting the data into a shared doc. This works when your checks are grouped by owner or tag—if every check is a flat list, the MCP can't segment the report by engineer. The integration also flags checks that fired more than 3 alerts in the review period, surfacing reliability trends without manual spreadsheet work. If your team runs these reviews weekly and has more than 10 checks to track, the MCP cuts 30 minutes of prep time per person.
Frequently asked
What does the Pingdom MCP do in Switchy?
It lets your AI assistant query Pingdom uptime checks, maintenance windows, alert actions, and account credits without leaving the conversation. You can ask questions like 'show me all failing checks' or 'list upcoming maintenance windows' and get live data. The MCP uses Pingdom's API under the hood, so results reflect your current monitoring state.
Do I need admin access to connect Pingdom?
You need a Pingdom API key with read permissions for the resources you want to query. Pingdom issues keys at the account level, so whoever generates the key controls which checks and contacts the MCP can see. If your team restricts API access, ask your Pingdom admin to create a key scoped to the checks you care about.
Can the Pingdom MCP create or edit uptime checks?
No. The MCP only reads data—it retrieves check lists, contact details, probe servers, and maintenance windows. If you need to create a new check or change alert thresholds, you still log into Pingdom's dashboard or use their full API directly. This keeps the MCP safe for read-only monitoring workflows.
Why use this instead of logging into Pingdom?
You skip context-switching when troubleshooting. Instead of opening Pingdom, filtering checks, and cross-referencing alert history, you ask your AI assistant 'which checks failed in the last hour' and get an answer in seconds. It's faster for triage, but you'll still use Pingdom's UI for configuration changes or detailed graphs.
Who on the team should connect the Pingdom MCP?
Whoever owns on-call rotations or incident response. They already have Pingdom access and know which checks matter. Once connected, anyone in your Switchy workspace can query the data, but the API key's permissions define what everyone sees. One connection per workspace is usually enough.