3,400+ MCP servers ready to use
Vinkius

Bring Uptime Monitoring
to VS Code Copilot

Learn how to connect Uptime.com to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Create CheckDelete CheckGet Account InfoGet CheckGet Check StatsGet Root Cause AnalysisList ChecksList Contact GroupsList IntegrationsList Monitoring NodesList Recent AlertsUpdate Check
Use with Your AI Agent
Ask AI about this MCP Server
ChatGPT Claude Perplexity

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)

create_check

g., HTTP, API). Create a new check

delete_check

Delete a monitor check

get_account_info

com account. Get account profile

get_check

Get check details

get_check_stats

Get check statistics

get_root_cause_analysis

Get alert RCA

list_checks

List all monitor checks

list_contact_groups

List contact groups

list_integrations

). List active integrations

list_monitoring_nodes

List global nodes

list_recent_alerts

List recent monitor alerts

update_check

Update a check

Why VS Code Copilot?

GitHub Copilot Agent mode brings Uptime.com data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • —

    VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • —

    Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • —

    Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • —

    GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Uptime.com in VS Code Copilot

AI Agent→Vinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Uptime.com and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Uptime.com to VS Code Copilot 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.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Use with Your AI Agent View step-by-step setup guide for VS Code Copilot →
Enterprise Security

Why teams choose Vinkius for Uptime.com in VS Code Copilot

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 VS Code Copilot 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.

Use with Your AI Agent View full Uptime.com details →
Uptime.com
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Uptime.com for VS Code Copilot

Every tool call from VS Code Copilot to the Uptime.com MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.