Pingdom MCP. Get real-time site status and performance metrics in chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Pingdom MCP Server lets you manage website reliability from a conversation. List all uptime checks, track average response times, check outage history, and pause monitoring—all through your AI client.
It gives SREs real-time status visibility without opening a single dashboard.
What your AI agents can do
Get average response time
Retrieves the average response time for a specified monitoring check.
Get check details
Pulls detailed information about a single, specific uptime check.
Get check outages
Lists all recorded outages for a specified monitoring check.
Lists all monitoring checks and retrieves their live status (up/down).
Fetches average response times or detailed outage logs for a specific monitored service.
Retrieves individual, granular log entries to diagnose specific errors or latency spikes.
Pauses or resumes an uptime check, useful for scheduled maintenance windows.
Lists all Pingdom probe locations and current alert notification contacts.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Pingdom MCP Server: 10 Tools for Website Monitoring
These tools give your AI client direct access to Pingdom's monitoring data. Use them to check statuses, audit logs, manage alerts, and track performance metrics.
019d75f3get average response time
Retrieves the average response time for a specified monitoring check.
019d75f3get check details
Pulls detailed information about a single, specific uptime check.
019d75f3get check outages
Lists all recorded outages for a specified monitoring check.
019d75f3list alert contacts
Retrieves the list of contacts configured to receive alerts.
019d75f3list check results
Lists individual log entries or results for a specific check.
019d75f3list maintenance windows
Shows all scheduled maintenance windows configured in Pingdom.
019d75f3list pingdom probes
Lists every monitoring location (probe) used by Pingdom worldwide.
019d75f3list uptime checks
Retrieves a list of all active uptime checks configured.
019d75f3pause uptime check
Temporarily halts the monitoring process for a specific uptime check.
019d75f3resume uptime check
Restarts an uptime check after it has been paused.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Pingdom, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Pingdom lets your AI client manage site reliability straight from a chat window. You don't gotta log into any dashboard; your agent handles all the dirty work.
To get a complete picture, you can first pull a rundown of every active uptime check configured using list_uptime_checks. This immediately tells you if everything’s running up or down in real time. If you need to dig deeper into one specific service, you can grab detailed info about that single check with get_check_details.
When it comes to performance history, you've got a few angles. You can retrieve the average response time for any given monitoring check using get_average_response_time. Want to see if the service has had problems? Running get_check_outages lists every recorded outage for that specific check so you know exactly when it went dark.
If those metrics aren't enough, you can get granular by calling list_check_results, which pulls individual log entries or results. This is what you use when a latency spike happens and you gotta see the raw data to figure out why.
For keeping things organized, you can check all scheduled maintenance windows using list_maintenance_windows. When it's time for planned work, you can temporarily halt monitoring with pause_uptime_check or restart it afterward by calling resume_uptime_check. These controls let you manage the system state without touching a button.
Understanding your infrastructure is key. You can check every single location Pingdom monitors worldwide by running list_pingdom_probes. If someone needs to know who gets paged when things go sideways, you pull that list of contacts with list_alert_contacts.
This setup means you've got full visibility—you can list all monitoring checks and see their live status (up/down). You analyze performance history by fetching average response times or viewing detailed outage logs for any monitored service. You examine raw check results to diagnose specific errors or latency spikes, getting those individual log entries.
You manage the monitoring state by pausing or resuming a check when needed for maintenance. Finally, you review global infrastructure by listing all Pingdom probe locations and checking the current alert notification contacts.
How Pingdom MCP Works
- 1 Subscribe to the server and input your Pingdom API Token.
- 2 Your AI client calls the necessary tool (e.g.,
list_uptime_checks) via the MCP protocol. - 3 The agent processes the raw monitoring data and presents a plain-language status report.
The bottom line is: you tell your agent what site health metric you need, and it gets the answer from Pingdom without you opening any web portals.
Who Is Pingdom MCP For?
This server is for DevOps Engineers or SREs who get tired of clicking through multiple dashboards during an incident. If your job involves checking site health under pressure, this saves time.
Monitors response time trends and verifies probe locations directly from the IDE or chat client.
Quickly checks if a service is down, audits recent outages, and manages alert contacts during incident triage.
Pauses uptime checks when maintenance is scheduled to prevent false alerts from triggering alarms.
What Changes When You Connect
- See immediate operational status by running
list_uptime_checks. You instantly know which services are UP or DOWN without navigating a web console. This is crucial for initial incident triage. - Diagnose slowdowns using
get_average_response_time. Instead of just seeing 'slow,' you get specific metrics, telling you if performance has spiked and when it happened. - Manage the system flow with controls like
pause_uptime_checkorresume_uptime_check. You can take action (pausing monitoring) during planned maintenance right from your chat prompt. - Audit past incidents by using
get_check_outagesorlist_check_results. You get raw, historical data to understand the root cause of a problem days after it happened. - Map out coverage by calling
list_pingdom_probes. You instantly confirm if your monitoring is actually working in all the necessary global regions.
Real-World Use Cases
Investigating an unexpected site outage
An alert fires for 'Checkout API.' Instead of opening the dashboard, you ask your agent: 'What was the last time Checkout API went down?' The agent runs get_check_outages, showing the exact date and duration. You then run list_check_results to grab the raw log data and determine if it was a timeout or a 503 error.
Preparing for scheduled downtime
The Ops team is updating the payment gateway. Instead of manually logging into Pingdom and remembering to pause checks, they prompt their agent: 'Pause all payments uptime checks until Friday.' The agent executes pause_uptime_check on every relevant service ID, guaranteeing no false alarms.
Analyzing performance before a major release
Before launching v2.0, you need to know if the 'Main Site' has degraded over time. You ask your agent for the average response time using get_average_response_time. The resulting metric shows stable performance (342ms), giving immediate sign-off.
Confirming monitoring coverage
The product team expands into Asia. You ask your agent to list all available probe locations using list_pingdom_probes. The agent returns the full global list, allowing you to confirm if a new market (like Tokyo) is covered by an active monitoring node.
The Tradeoffs
Treating status checks as logs
Relying only on the 'DOWN' alert without checking history. You see the site is down, but you don't know if it was a one-off failure or a persistent issue.
→
First, run list_uptime_checks to confirm the current status. Then, immediately use get_check_outages to pull the full history. This tells you if the outage is an anomaly or part of a pattern.
Ignoring maintenance protocols
Running routine checks while development is actively working on the site. The system throws false alarms because changes are breaking things temporarily.
→
Before any scheduled work, always use list_maintenance_windows to review planned downtime. Then, proactively run pause_uptime_check for the affected services.
Overlooking global coverage
Assuming that because your main office is in New York, all traffic will be monitored correctly. You might miss performance issues happening overseas.
→
Run list_pingdom_probes to verify the full geographical spread of monitoring nodes. Confirming this list ensures you aren't blind to regional performance dips.
When It Fits, When It Doesn't
Use Pingdom MCP if your primary job involves diagnosing site health, not just viewing it. If you only need a simple 'Is it up?' answer, the initial list_uptime_checks tool is enough. However, for true reliability work—the kind that prevents incidents—you must layer tools. Don't stop at status: if anything shows as 'down,' run get_check_outages. If performance looks weird, use get_average_response_time. Only when you need to change the monitoring itself (e.g., pausing checks) do you touch state-changing functions like pause_uptime_check. Never assume a tool covers everything; check both list_alert_contacts and list_maintenance_windows before assuming your current alerts are accurate.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Pingdom. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Site health checks shouldn't require logging into three different dashboards.
Right now, if a client reports slow performance, you open the main uptime dashboard. Then, because it’s vague, you have to switch tabs to check historical data in the 'Outages' section. Finally, you jump to the metrics tab just to get an average number—all while copy-pasting IDs and remembering which browser window has the most useful log.
With this MCP server, you talk to your agent: 'What was the average response time for the Checkout API last week?' The agent runs `get_average_response_time` and spits out one clean number. That's it. You get the precise metric without switching a tab or opening a single web portal.
Pingdom MCP Server: Control monitoring state with simple prompts.
Historically, if you knew maintenance was coming up, you had to manually log into the Pingdom UI and find every single check related to the service. You'd then have to click 'pause' for each one individually. Missing even one meant false alarms during critical hours.
Now, your agent handles it. Just tell it: 'Pause all checks for payments.' The server executes `pause_uptime_check` across all necessary services, guaranteeing a clean slate and zero false alerts for the duration of the maintenance window.
Common Questions About Pingdom MCP
How do I check if my site is currently up or down using Pingdom MCP Server? +
Run list_uptime_checks. This tool lists all your configured checks and shows their real-time status (UP, DOWN, etc.) immediately.
I need to know why a site failed last week. Can I use get_check_outages? +
Yes, get_check_outages lists all recorded outages for a specific check, giving you the timeline and details of past failures.
What is the best way to find out if Pingdom monitors my new region? Use list_pingdom_probes. +
Use list_pingdom_probes to get a full inventory of every monitoring location. This verifies your global coverage before you launch in a new area.
I need to pause checks for maintenance, but which tool should I use? Is it pause_uptime_check? +
Use pause_uptime_check. It takes the ID of a specific uptime check and temporarily stops monitoring until you run resume_uptime_check.
Can I get raw logs for an error? Which Pingdom tool should I use? +
Use list_check_results. This retrieves individual, granular log entries that help you pinpoint the exact cause of a latency spike or failure.
How can I use `get_average_response_time` to track performance trends for a check? +
It retrieves the average response time. You input the specific Check ID, and the tool gives you the mean performance metric over a selected historical window. This helps you spot gradual degradation that status checks miss.
What information does the `get_check_details` tool provide about a single uptime check? +
It delivers full configuration data for one specific check. Beyond just its current status, this includes details like the target URL, check interval, and monitoring type. Use it when you need to audit how Pingdom is checking the site.
After using `pause_uptime_check`, what tool should I use to reactivate the service? +
You must call resume_uptime_check. Just provide the unique ID of the check you want running again. This immediately restores monitoring and sends out alerts if the site fails post-maintenance.
How do I create a Pingdom API Token? +
In your Pingdom dashboard (or SolarWinds portal), go to Settings > API Tokens. Click Add API Token, give it a name, and ensure it has the necessary access levels.
Can I see response times for different global regions? +
Yes! The list_check_results tool returns data from multiple probe locations, allowing you to see how your site performs from different parts of the world.
Does this support pausing multiple checks at once? +
The tools handle checks individually, but you can ask the AI agent to 'Pause all checks related to our API' and it will process them sequentially using their IDs.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Zapier
Monitor automated workflows, audit app connections, and search for Zap templates on Zapier — the leader in AI orchestration.
Jira Software Cloud
Manage Jira Software Agile workflows — list boards, track sprints, manage backlogs, and inspect epics directly from your AI agent.
NVIDIA API Catalog
Cloud Engine proxy running native foundational completions natively utilizing active Nemotron and Llama3 architectures.
You might also like
Doppler
Manage secrets and environment variables via Doppler — list projects, audit secrets, and track activity logs from any AI agent.
Nabis
Cannabis wholesale and distribution — manage orders, inventory, and retailers via Nabis.
Netease Yunxin / 网易云信
Massive scale RTC and IM platform — manage user accounts, chat groups, and messaging via AI.