← Registry

DevOps

uptimex.co

An MCP server for creating, updating, deleting, and testing uptime monitors and retrieving monitor status and 24-hour statistics.

1 endpoint5 known toolsFirst detected November 15, 2026Last detected November 15, 2026

ENDPOINT 1

https://api.uptimex.co/mcp

No auth detected

MCP server metadata

Name
uptimex
Version
1.0.0
Capabilities
toolsprompts
Server instructions

UptimeX watches the uptime of URLs. Use these tools to manage the user's monitors for them. To create a monitor you need at least a `url`. Optional fields: name (defaults to the host), method (HEAD by default; auto-switches to GET when content_rules are set), interval_sec (plan minimum: 300s free / 60s pro), expect_status (exact code; omit for any 2xx/3xx), content_rules (up to 4 body checks), request_headers (up to 4, for auth), request_body (write methods only — checks run on a schedule, so point writes at test data or a dedicated test route, never real customer writes), fail_threshold, recover_threshold. Fill missing details from the conversation, the user's memory/context, or by asking one or two concise questions — prefer sensible defaults over interrogating. A bare URL is enough to start. Call list_monitors first to avoid duplicates. Briefly confirm what you'll add before creating, and report the resulting status afterward. You can also update_monitor (partial edits, incl. enabled:false to pause) and delete_monitor. If create fails with monitor_limit the user is at their plan cap — tell them.

Known tools 5

list_monitors

List all of the authenticated user's monitors with current status and 24h stats.

Inferred read-only
create_monitor

Create a monitor.

Potential side effects
update_monitor

Update fields of an existing monitor (partial).

Potential side effects
delete_monitor

Delete a monitor by id.

Potential side effects
test_monitor

Run one check against a draft config without saving.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.uptimex]
url = "https://api.uptimex.co/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "uptimex": {
      "type": "http",
      "url": "https://api.uptimex.co/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: uptimex
Remote MCP URL: https://api.uptimex.co/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "uptimex": {
      "url": "https://api.uptimex.co/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "uptimex": {
      "type": "http",
      "url": "https://api.uptimex.co/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "uptimex",
  "transport": "streamable-http",
  "url": "https://api.uptimex.co/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for uptimex.co was fetched 2026-11-16T20:09:18.022Z.

Trust status Neutral

uptimex.co is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.