# Healthchecks.io MCP > Healthchecks.io monitors scheduled background jobs and cron tasks, letting you track service uptime directly through your AI agent. Quickly list active checks, inspect ping histories, and pause or resume monitoring to debug failed infrastructure runs without leaving your chat window. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** cron-jobs, uptime-monitoring, background-tasks, alerting, infrastructure-monitoring ## Description When a critical back-end process fails at 3 AM, you don't want to jump between dashboards. This MCP connects Healthchecks.io directly to your workflow, giving your agent the visibility it needs to manage system health through plain conversation. You can ask your AI client to list all monitoring checks or inspect specific ping bodies to figure out exactly why a job failed. Need to temporarily stop alerts while you deploy? Your agent handles that too. This connection works with any MCP-compatible client and centralizes complex infrastructure auditing, making it one of the most powerful developer tools available in the Vinkius catalog. ## Tools ### create_check Creates a brand new monitoring check for an infrastructure component. ### delete_check Removes an existing monitoring check from the system. ### get_check Retrieves all details about a specific check using its unique ID or key. ### get_ping_body Fetches the raw data payload that was included with a specific ping. ### get_status Checks the overall health status of the entire Healthchecks.io monitoring service. ### list_badges Lists all predefined status badges available for displaying project health. ### list_checks Retrieves a list of all active monitoring checks, optionally filtered by tags or identifiers. ### list_flips Lists the historical record of status changes (up/down) for a specific check. ### list_integrations Shows all configured notification channels, such as Slack or email alerts. ### list_pings Provides a list of the most recent ping events associated with a given check. ### pause_check Temporarily suspends monitoring for a specified check to prevent false alerts. ### resume_check Restores active monitoring status for a previously paused check. ### update_check Modifies the settings or parameters of an already existing check. ## Prompt Examples **Prompt:** ``` List all my active checks and their current status. ``` **Response:** ``` I've retrieved your checks. You have 3 active monitors: 'Daily Backup' (Up), 'Hourly Sync' (Up), and 'Cleanup Script' (Down). Would you like to see the pings for the 'Cleanup Script'? ``` **Prompt:** ``` Show me the last 5 pings for check uuid '550e8400-e29b-41d4-a716-446655440000'. ``` **Response:** ``` Here are the last 5 pings for that check. The most recent was 10 minutes ago with a 'success' status. Ping #452 included a payload of 1.2KB. Do you want to inspect the body of any specific ping? ``` **Prompt:** ``` Create a new check named 'Database Backup' with a 24-hour timeout. ``` **Response:** ``` I've created the 'Database Backup' check. The UUID is 'a1b2c3d4...'. You can now send pings to `https://hc-ping.com/a1b2c3d4...`. I've set the timeout to 86400 seconds as requested. ``` ## Capabilities ### Manage Monitoring Checks Create, read, update, or delete checks to define what services need monitoring. ### Review Ping History Retrieve a list of recent pings and inspect the full payloads to debug successful or failed tasks. ### Track Status Changes View historical status changes (flips) for any monitored service over time. ### Control Check State Pause or resume an entire check to manage alerts during maintenance windows. ### Inspect Notifications List all configured notification channels to confirm that team alerts are going to the right places. ## Use Cases ### Debugging a Payment Gateway Sync Failure A user asks their agent to check the payment sync job. The agent lists pings, finds the most recent failure, and then uses `get_ping_body` to confirm that the payload was missing the required transaction ID, solving the issue instantly. ### Pre-Release Maintenance Window An SRE team member tells their agent, 'We're deploying version 3.0; pause all checks related to user signups.' The agent uses `pause_check` for the specified checks, ensuring no false alerts interrupt the critical deployment process. ### Inventory Check of Background Tasks A new developer asks their agent, 'Show me every check related to user data cleanup.' The agent calls `list_checks` and filters the results by tags, giving them a complete inventory without manually browsing multiple dashboards. ### Verifying Alert Channels A team lead wants to confirm that critical alerts are going to Slack. They ask their agent to list integrations, confirming which notification channels are active and configured correctly before the next major release. ## Benefits - Stop context switching: Instead of opening a browser, navigating to the dashboard, and filtering logs, you just tell your agent to list pings for a check. The data appears instantly in your chat history. - Pinpoint failure causes: If a job fails, you don't just get an 'error.' You ask your agent to retrieve the ping body, which gives you the exact payload that triggered the crash, saving minutes of painful debugging. - Control alerts on demand: Need to deploy? Use the `pause_check` tool through your agent. When the deployment is done, tell it to `resume_check`. It's simple, conversational control over critical infrastructure monitoring. - Audit coverage easily: You can use `list_checks` to get a full inventory of every scheduled task being monitored in a project, helping you audit compliance or spot blind spots quickly. - Visualize history: Beyond just knowing if it passed or failed, your agent lets you list flips, showing the precise timeline and number of times a service transitioned from 'up' to 'down', giving deep operational insights. ## How It Works The bottom line is: you treat complex infrastructure auditing exactly like a chat command. 1. Subscribe to this MCP and provide your Healthchecks.io API Key. 2. Your AI agent connects using the key, granting it access to your monitoring accounts. 3. You interact with the system by asking your agent to perform actions like listing checks or retrieving ping bodies. ## Frequently Asked Questions **How do I list all my active checks using the Healthchecks.io MCP?** You use the `list_checks` tool through your agent. This command pulls a comprehensive inventory of every monitoring check in your project, letting you see what's covered and what isn't. **Can I pause alerts using Healthchecks.io MCP?** Yes. You use the `pause_check` tool to temporarily suspend monitoring for any specific check. This is perfect for maintenance windows or controlled deployments when you don't want false alarms. **What is the best way to debug a failed task with Healthchecks.io MCP?** The most effective way is to first use `list_pings` and then request the raw data payload using `get_ping_body`. This shows you the exact input that caused the failure. **Does Healthchecks.io MCP handle status history?** It does. You can use the `list_flips` tool to track every single transition—from 'up' to 'down' and back again—giving you a full audit trail of service stability. **How do I confirm that my team gets alerts for critical jobs?** You use the `list_integrations` tool. This shows all configured notification channels, allowing you to verify which services are correctly alerting your team.