Skip to content

UptyBots MCP server

com.uptybots/monitoringuptybots.comstreamable-httpv1.4.1Scanned

Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

15 tools: 1 can delete or cancel things, 8 change things and 6 only read.

Tools: 1 delete, 0 irreversible, 8 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 15
  • Can send data out · 6
  • 1 finding

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 UptyBots MCP server can do

The UptyBots MCP server is published by uptybots.com, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (1 tool: delete_monitor) and create or change data (8 tools: create_http_monitor, create_api_monitor, create_ping_monitor, create_port_monitor and 4 more). 6 tools only read.

1 tool reads private data (get_notifications); 15 tools bring in text other people can write (list_monitors, get_monitor, create_http_monitor and 12 more); 6 tools can send data out of your system (create_http_monitor, create_api_monitor, create_ping_monitor and 3 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.4.1.

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.

15 tools

Deletes or cancels 1Claude Code: deny
  • delete_monitorPermanently delete a monitor together with its entire check history, incidents and statistics.Reads text others writeNo findings

    Why it is in this group

    • The name "delete_monitor" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Permanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash to restore from. Confirm with the user before calling it, and prefer pause_monitor whenever the intent is only to stop the checking for a while.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 8Claude Code: ask
  • create_api_monitorWatch a JSON or REST endpoint where the response itself matters, not only that the host answered.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch a JSON or REST endpoint where the response itself matters, not only that the host answered. Use it for health endpoints, webhooks and any API whose failure would be invisible to a plain page check. For an ordinary web page, create_http_monitor is lighter and enough.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_domain_monitorWatch a domain registration and report how long is left before it lapses, read from WHOIS.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch a domain registration and report how long is left before it lapses, read from WHOIS. This catches the failure no uptime check can see: everything works perfectly right up to the day the domain expires. Distinct from create_ssl_monitor, which watches the certificate rather than the registration; the two expire on different dates and both are worth watching.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_http_monitorWatch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime. This is the right type for anything a browser would open. Choose create_api_monitor instead when the response body matters as well as the status code. Checks run from probes in several countries. Call list_monitors first so you do not create a duplicate of an existing url.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_ping_monitorWatch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss. Use it for servers, routers and anything with no web service on top. It says nothing about whether a site or service on that host is working - a box can ping perfectly while its web server is down. Some hosting providers block ICMP, in which case the monitor will read as down.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_port_monitorWatch one TCP or UDP port on a host and report it up only when the service behind it actually answers.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_ssl_monitorWatch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Watch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires. This is about the certificate, not about the site being reachable - pair it with create_http_monitor when you want both. Note that such a monitor carries two independent states, one for reachability and one for expiry, so a certificate can be days from expiring while the check still reads up.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • pause_monitorStop checking a monitor without deleting it.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one is off.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • resume_monitorStart checking a paused monitor again, with the configuration it had before.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the current state is known within moments. Safe to call on a monitor that is already running.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • get_incidentsRead the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text, and which probe saw…Reads text others writeNo findings

    Why it is in this group

    • The name "get_incidents" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text, and which probe saw it. This is the tool for "what happened" and "how often does this break". For the shape of response times around an outage, follow up with get_stats_hourly.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_monitorRead one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protocol for PORT, certific…Reads text others writeNo findings

    Why it is in this group

    • The name "get_monitor" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protocol for PORT, certificate or registration expiry date for SSL and DOMAIN. Use it after list_monitors when the answer depends on how the check is configured, for instance whether a timeout is too tight or which port is actually being watched.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_notificationsRead the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_notifications" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Read the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each. Use it to answer "was I actually told about this outage" and to find a channel that is silently failing - a monitor can be detecting downtime correctly while its webhook has been rejecting every delivery. Covers the whole account, not one monitor.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_stats_dailyResponse time and uptime for one monitor aggregated per day, with min, max, average and p95.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stats_daily" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Response time and uptime for one monitor aggregated per day, with min, max, average and p95. This is the tool for reports and trends over weeks or months, and for comparing one monitor against another over the same window. When a single day looks wrong, zoom into it with get_stats_hourly.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_stats_hourlyResponse time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stats_hourly" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Response time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket. Use it to see the shape of a problem: whether a service degrades before it fails, whether outages cluster at a particular time of day, or how long a single incident really lasted. Best over hours or days; for weeks and months use get_stats_daily instead, which returns far fewer rows.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_monitorsList the monitors on the account, newest first, 30 per page.Reads text others write1 finding

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...ge. Each entry carries the id needed by every other tool, plus name, url, type, current status,..."

      What this check looks for
    Description, as the server wrote it
    List the monitors on the account, newest first, 30 per page. Each entry carries the id needed by every other tool, plus name, url, type, current status, check frequency and the uptime percentage over the last 24 hours. Start here when the request names a monitor by name rather than by id, and when asked what is broken - filtering by status "down" answers that in one call. Returns an empty list rather than an error when nothing matches.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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.

90 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out6
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__monitoring__get_notifications"
    ]
  }
}

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 20, 2026, 18:49 UTC, unchanged since Oct 22, 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
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.uptybots.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://uptybots.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

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

    Matched text

    https://mcp.uptybots.com/mcp: tools/list returned 15 tools to an anonymous client, including delete_monitor (destructive), create_http_monitor (write), create_api_monitor (write), create_ping_monitor (write), create_port_monitor (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...ge. Each entry carries the id needed by every other tool, plus name, url, type, current status,..."

    What this check looks for

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.4.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http monitoring https://mcp.uptybots.com/mcp
claude mcp add --transport http monitoring https://mcp.uptybots.com/mcp

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__monitoring__list_monitors",
      "mcp__monitoring__get_monitor",
      "mcp__monitoring__get_incidents",
      "mcp__monitoring__get_stats_hourly",
      "mcp__monitoring__get_stats_daily",
      "mcp__monitoring__get_notifications"
    ],
    "ask": [
      "mcp__monitoring__create_http_monitor",
      "mcp__monitoring__create_api_monitor",
      "mcp__monitoring__create_ping_monitor",
      "mcp__monitoring__create_port_monitor",
      "mcp__monitoring__create_ssl_monitor",
      "mcp__monitoring__create_domain_monitor",
      "mcp__monitoring__pause_monitor",
      "mcp__monitoring__resume_monitor"
    ],
    "deny": [
      "mcp__monitoring__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 monitoring. Review it before you use it.

Capability tags behind 15 rules
  • mcp__monitoring__list_monitors untrusted-input
  • mcp__monitoring__get_monitor untrusted-input
  • mcp__monitoring__create_http_monitor untrusted-input, outbound
  • mcp__monitoring__create_api_monitor untrusted-input, outbound
  • mcp__monitoring__create_ping_monitor untrusted-input, outbound
  • mcp__monitoring__create_port_monitor untrusted-input, outbound
  • mcp__monitoring__create_ssl_monitor untrusted-input, outbound
  • mcp__monitoring__create_domain_monitor untrusted-input, outbound
  • mcp__monitoring__pause_monitor untrusted-input
  • mcp__monitoring__resume_monitor untrusted-input
  • mcp__monitoring__delete_monitor untrusted-input
  • mcp__monitoring__get_incidents untrusted-input
  • mcp__monitoring__get_stats_hourly untrusted-input
  • mcp__monitoring__get_stats_daily untrusted-input
  • mcp__monitoring__get_notifications private-data, untrusted-input

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/com.uptybots/monitoring/verify?hash=7dcdd0147d12bbe59a23bf5e87080e4d83a3ebe1dd55e952d6cef6d4064db851" | jq -e '.changed == false'

Pinned hash 7dcdd0147d12, from Nov 14, 2026, 16:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.uptybots/monitoring/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.

UptyBots MCP server: questions and answers

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

Is the UptyBots MCP server safe?

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

Can the UptyBots MCP server delete data?

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

Can the UptyBots 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 UptyBots MCP server have?

15 tools: 1 destructive, 8 write, 6 read. delete_monitor, create_http_monitor, create_api_monitor, create_ping_monitor, create_port_monitor, create_ssl_monitor, create_domain_monitor, pause_monitor and 7 more.

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

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

Does the UptyBots MCP server send data to outside services?

6 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_http_monitor, create_api_monitor, create_ping_monitor, create_port_monitor, create_ssl_monitor and create_domain_monitor.

Has the UptyBots MCP server changed its tools?

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