Skip to content

UptimeX MCP server

co.uptimex/uptimexuptimex.costreamable-httpv1.0.0Scanned

Create, test, and manage uptime monitors for websites and APIs from your AI agent.

5 tools: 1 can delete or cancel things, 3 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the UptimeX MCP server can do

The UptimeX MCP server is published by uptimex.co, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: delete_monitor) and create or change data (3 tools: create_monitor, update_monitor and test_monitor). 1 tool only reads.

3 tools can send data out of your system (create_monitor, update_monitor and test_monitor).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Deletes or cancels 1Claude Code: deny
  • delete_monitorDelete a monitor by id.No findings

    Why it is in this group

    • The name "delete_monitor" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete a monitor by id.
Changes things 3Claude Code: ask
  • create_monitorCreate a monitor.Can send data outNo findings

    Why it is in this group

    • The name "create_monitor" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Create a monitor. Returns the created monitor.
  • test_monitorRun one check against a draft config without saving.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run one check against a draft config without saving. Returns the check result.
  • update_monitorUpdate fields of an existing monitor (partial).Can send data outNo findings

    Why it is in this group

    • The name "update_monitor" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Update fields of an existing monitor (partial). Only provided fields change.
Only reads 1Show 1 read-only tool
  • list_monitorsList all of the authenticated user's monitors with current status and 24h stats.No findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    List all of the authenticated user's monitors with current status and 24h stats.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.uptimex.co/mcp: tools/list returned 5 tools to an anonymous client, including delete_monitor (destructive), create_monitor (write), update_monitor (write), test_monitor (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http uptimex https://api.uptimex.co/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http uptimex https://api.uptimex.co/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__uptimex__list_monitors"
    ],
    "ask": [
      "mcp__uptimex__create_monitor",
      "mcp__uptimex__update_monitor",
      "mcp__uptimex__test_monitor"
    ],
    "deny": [
      "mcp__uptimex__delete_monitor"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as uptimex. Review it before you use it.

Capability tags behind 3 rules
  • mcp__uptimex__create_monitor outbound
  • mcp__uptimex__update_monitor outbound
  • mcp__uptimex__test_monitor outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.uptimex/uptimex/verify?hash=751d0ffa30a6c95a9b4123812ebac6337443f80b67c0507c15b8016557d2a0ce" | jq -e '.changed == false'

Pinned hash 751d0ffa30a6, from Nov 15, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.uptimex/uptimex/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.uptimex/uptimex
[![Anlyon Radar](https://radar.anlyon.com/badge/co.uptimex/uptimex.svg)](https://radar.anlyon.com/servers/co.uptimex/uptimex)

Source: MCP Registry. Synced Nov 15, 2026, 09:17 UTC.

UptimeX MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the UptimeX MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the UptimeX MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_monitor.

Can the UptimeX MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the UptimeX MCP server have?

5 tools: 1 destructive, 3 write, 1 read. delete_monitor, create_monitor, update_monitor, test_monitor and list_monitors.

Does the UptimeX MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the UptimeX MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor, update_monitor and test_monitor.

Has the UptimeX MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.