Bring Uptime Monitoring
to Windsurf
Learn how to connect Uptime.com to Windsurf 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 Windsurf?
Windsurf's Cascade agent chains multiple Uptime.com tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 12 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 12 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
Uptime.com in Windsurf
Uptime.com and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Uptime.com to Windsurf 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 Windsurf
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 Windsurf 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 Windsurf
Every tool call from Windsurf 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 Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.