# Uptime.com MCP for AI Agents AI Agent Connect

> Uptime.com MCP lets you manage website and API monitoring directly through your AI client. You can create new checks, pull recent alert histories, and get detailed root cause analysis for outages without leaving your workspace. It connects to your Uptime.com account to give your agent visibility into global monitoring nodes and notification flows.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_JT4XXpvgrf6pheCWiyox80PA6iEujLlkIuZeJAx8/ai-agent-connect
- **Tags:** uptime-monitoring, site-reliability, api-monitoring, incident-alerts, root-cause-analysis, network-diagnostics

## Description

Managing site reliability usually feels like jumping between tabs to check if an API is down, why it's down, and who needs to know about it. This Connector changes that by putting your entire Uptime.com dashboard into your AI client. Instead of hunting for specific monitor IDs or digging through old logs, you can just ask your agent for the status of your staging environment or request a summary of recent outages. It handles the heavy lifting of pulling performance data and identifying the specific reason for a failure. When you need to set up a new check or update a contact group, you just tell the agent what to do. It's a way to turn your monitoring strategy into a conversation, making it much easier to keep your services online and your team informed. You can find this and thousands of other connections in the Vinkius catalog to get your tools working together.

## Tools

### get_account_info
Get your account profile details. This helps you verify your connection and account status.

### get_check
Get specific details for a single monitor check. Use it to see the exact configuration of a single endpoint.

### get_root_cause_analysis
Get the alert RCA. This pulls the specific reason for a failure to help you fix things faster.

### list_checks
List all monitor checks

### list_contact_groups
List contact groups. Use this to see who gets notified when a service goes down.

### list_integrations
List active integrations. This shows your connected tools like Slack or PagerDuty.

### list_monitoring_nodes
List global nodes. This helps you see where your checks are running geographically.

### create_check
Create a new HTTP, API, or ICMP monitor check. This lets you add new endpoints to your monitoring suite instantly.

### delete_check
Remove an existing monitor check. Use this to clean up old monitors or decommission services.

### get_check_stats
Get check statistics. Use this to see uptime percentages and response times over time.

### list_recent_alerts
List recent monitor alerts. This gives you a quick look at what's been going wrong lately.

### update_check
Update a check. Use this to modify the settings of an existing monitor without using the web UI.

## Prompt Examples

**Prompt:** 
```
What's the status of my monitors?
```

**Response:** 
```
I've checked your active monitors. Here is the current status:

| Monitor Name | Status | Uptime (30d) |
| :--- | :--- | :--- |
| **Main Website** | ✅ UP | 99.98% |
| **API Gateway** | ✅ UP | 99.95% |
| **Staging Server** | ❌ DOWN | 94.20% |

Would you like me to pull the RCA for the **Staging Server**?
```

**Prompt:** 
```
Show me the recent alerts.
```

**Response:** 
```
I've fetched the recent alert history for you:

*   **Staging Server**: Down for 15m (Resolved)
*   **API Gateway**: Down for 2m (Resolved)

Both services are currently back online. Let me know if you need more details on either of these.
```

**Prompt:** 
```
Give me the RCA for the API Gateway.
```

**Response:** 
```
I've retrieved the Root Cause Analysis for the **API Gateway** outage:

*   **Issue**: Connection Timeout
*   **Root Cause**: The database connection pool was exhausted due to a spike in traffic from the marketing campaign.
*   **Resolution**: Auto-scaled the database instances and cleared the pool.

Is there anything else you need to know about this incident?
```

## Capabilities

### Create new HTTP or API monitor checks
Add new endpoints to your monitoring suite instantly through natural language commands.

### Retrieve a history of recent uptime transitions
Get a quick look at recent up and down events to see how your services have behaved lately.

### Get detailed root cause analysis for specific alerts
Pull the specific reason for a failure to help you identify and fix issues faster.

### Query performance statistics for any monitor
See uptime percentages and average response times for any specific check in your account.

### Manage contact groups and third-party integrations
Audit and update who gets notified when a service goes down across Slack, PagerDuty, and other tools.

### List global monitoring nodes for coverage checks
Verify exactly where your checks are running geographically to ensure global coverage.

## Use Cases

### The Midnight Outage
An SRE gets an alert and asks the agent to list recent alerts and give them the RCA for the staging API to find the fix immediately.

### The New Deployment
A web admin tells the agent to create a new HTTP check for a new landing page right after a production push.

### The Reliability Audit
A product owner asks the agent to find the uptime percentage for the main site over the last 30 days for a stakeholder report.

### The Notification Cleanup
A DevOps lead asks the agent to list active integrations and contact groups to see who is getting paged for specific alerts.

## Benefits

- Stop manual tab switching by querying your Uptime.com dashboard directly through your AI client.
- Get faster incident resolution by using get_root_cause_analysis to see exactly why a service failed.
- Manage your entire monitoring fleet by using create_check and update_check to modify endpoints on the fly.
- Keep your team informed by checking list_contact_groups and list_integrations to audit your notification paths.
- Track your service's health over time by pulling data with get_check_stats for quick reporting.
- Verify your global coverage by using list_monitoring_nodes to see exactly where your checks are running.

## How It Works

The bottom line is you get a conversational interface for your entire uptime monitoring and incident response workflow.

1. Subscribe to the Uptime.com MCP on Vinkius.
2. Add your Uptime.com API Token to your configuration.
3. Ask your AI client to check status, create monitors, or pull RCA reports.

## Frequently Asked Questions

**Can I use Uptime.com MCP to see why my site is down?**
Yes, it pulls the Root Cause Analysis (RCA) for your alerts. This means you can ask your agent to explain the specific reason for a failure, like a database timeout or a 500 error, without digging through logs.

**Does Uptime.com MCP support API monitoring?**
Yes, it supports HTTP, API, and ICMP checks. You can use your agent to create new monitors for your endpoints or check their current status.

**How do I connect Uptime.com MCP to my AI client?**
You just need to subscribe to the Connector and provide your Uptime.com API Token. Once connected, you can manage your entire monitoring account through your chat interface.

**Can I see my global coverage with Uptime.com MCP?**
Yes, you can ask your agent to list your global monitoring nodes. This helps you see exactly which geographic locations are checking your site's health.

**Can I manage my Slack alerts with Uptime.com MCP?**
Yes, you can use the Connector to list your active integrations and contact groups. This allows you to audit who is receiving notifications and ensure your team is being alerted correctly.

**Can I update my monitor settings using Uptime.com MCP?**
Yes, you can use the update tool to modify existing checks. This lets you change things like URLs, intervals, or retry logic using natural language instead of the web dashboard.

**Can I see the reason why my website went down via AI?**
Yes! Use the `get_root_cause_analysis` tool and provide the Alert ID (PK). Your agent will retrieve the detailed RCA report explaining the failure.

**How do I create a new HTTP check to monitor a URL?**
Use the `create_check` action. Provide the name, address (URL), and set the `check_type` to 'HTTP'. The agent will instantly register the new monitor.

**Is it possible to see the performance statistics for a monitor?**
Absolutely. Run the `get_check_stats` query with your Check ID to retrieve performance and uptime metrics for that specific service.