Bring Uptime Monitoring
to Claude Desktop
Learn how to connect Uptime.com to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Uptime.com MCP Server?
Connect your Uptime.com monitoring account to any AI agent and simplify how you monitor site reliability, manage alerts, and perform root cause analysis through natural conversation.
What you can do
- Check Management — List, create, and update monitor checks (HTTP, API, ICMP) to ensure your services are always online.
- Alert Oversight — Retrieve a history of recent UP/DOWN transitions and stay notified of critical outages.
- Incident Analysis — Get detailed Root Cause Analysis (RCA) for alerts to understand why a failure occurred.
- Performance Metrics — Query uptime statistics and performance data for any specific monitor check.
- Team Coordination — List contact groups and third-party integrations (Slack, PagerDuty) to manage notification flows.
- Infrastructure Monitoring — List global monitoring nodes to understand your testing coverage.
How it works
1. Subscribe to this server
2. Enter your Uptime.com API Token (found in your account settings)
3. Start monitoring your uptime from Claude, Cursor, or any MCP client
Who is this for?
- SRE & DevOps Engineers — quickly retrieve RCA reports and check performance stats via simple AI queries.
- Web Administrators — create new monitor checks and verify site health directly from the workspace.
- Product Owners — monitor uptime metrics and recent alert history to measure service reliability via the AI assistant.
Built-in capabilities (12)
g., HTTP, API). Create a new check
Delete a monitor check
com account. Get account profile
Get check details
Get check statistics
Get alert RCA
List all monitor checks
List contact groups
). List active integrations
List global nodes
List recent monitor alerts
Update a check
Why Claude Desktop?
Claude Desktop is the definitive way to connect Uptime.com to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Uptime.com in Claude Desktop
Uptime.com and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Uptime.com to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Uptime.com in Claude Desktop
The Uptime.com MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Uptime.com for Claude Desktop
Every tool call from Claude Desktop to the Uptime.com MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.