Skip to content

OhSnap uptime monitoring MCP server

io.ohsnap/mcpohsnap.iostreamable-httpv1.0.1Scanned

Check if a website is down, add websites to monitor, read outage history and send test alerts.

6 tools: 1 do something that can't be undone, 2 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. 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 OhSnap uptime monitoring MCP server can do

The OhSnap uptime monitoring MCP server is published by ohsnap.io, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_test_alert) and create or change data (2 tools: check_website and add_monitor), but cannot delete data. 3 tools only read.

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

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.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.

6 tools

Can't be undone 1Claude Code: ask
  • send_test_alertSends a clearly labelled test DOWN alert through every alert channel linked to a website (email, SMS, WhatsApp, Slack, Telegram), so the user can confirm alerts reach them.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_test_alert" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_test_alert" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends a clearly labelled test DOWN alert through every alert channel linked to a website (email, SMS, WhatsApp, Slack, Telegram), so the user can confirm alerts reach them. Limited to one test per website per minute.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • add_monitorAdds a website to OhSnap so it is checked around the clock and the user is alerted when it goes down or comes back.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "add_monitor" says "add": 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
    Adds a website to OhSnap so it is checked around the clock and the user is alerted when it goes down or comes back. Free accounts can monitor 5 sites every 5 minutes; Pro allows up to 100 every 30 seconds, and Agency any number. Pass alert_email if the account has no alert channel yet, otherwise the website will run silently. A URL the account already monitors is not added twice: the existing monitor is returned, so a retry is safe. SMS, WhatsApp, Slack and Telegram alerts are configured in the OhSnap dashboard.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_websiteOne-off check of whether a website is up right now, from OhSnap's probe network.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    One-off check of whether a website is up right now, from OhSnap's probe network. Works without an account. Use when the user asks "is my site down?", "is X up?", or wants a status code, response time, or the reason a site fails (DNS failure, SSL error, timeout, HTTP error, Cloudflare edge error). Results are cached for 60 seconds per site, and each user can run 10 checks per minute.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_incidentsReturns recent outages for one monitored website: when each started and ended, how long it lasted, and the error.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 description's first sentence says "return" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns recent outages for one monitored website: when each started and ended, how long it lasted, and the error. On the Pro plan each incident includes an AI diagnosis in plain language; on Free it is marked ai_locked.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_monitorsLists every website this OhSnap account monitors, with its current status (up, down, warning, pending), last response time, and check interval.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists every website this OhSnap account monitors, with its current status (up, down, warning, pending), last response time, and check interval. Use to answer "are my sites up?" and to find a website_id for other tools.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • whoamiReturns the OhSnap account this MCP key belongs to: email, plan (Free, Pro, Agency), the monitor cap, and the fastest allowed check interval.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Returns the OhSnap account this MCP key belongs to: email, plan (Free, Pro, Agency), the monitor cap, and the fastest allowed check interval. Call before add_monitor to explain plan limits up front.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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.

18 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.
Reads text others write6
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__ohsnap__whoami"
    ]
  }
}

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, 19:13 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
3
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 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.ohsnap.io/mcp: tools/list returned 6 tools to an anonymous client, including send_test_alert (irreversible), check_website (write), add_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.

  1. Tools3 changed.~3 changedView diff
  2. Tools3 changed.~3 changedView diff

Install

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

claude mcp add --transport http ohsnap https://mcp.ohsnap.io/mcp
claude mcp add --transport http ohsnap https://mcp.ohsnap.io/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__ohsnap__whoami",
      "mcp__ohsnap__list_monitors",
      "mcp__ohsnap__get_incidents"
    ],
    "ask": [
      "mcp__ohsnap__check_website",
      "mcp__ohsnap__add_monitor",
      "mcp__ohsnap__send_test_alert"
    ],
    "deny": []
  }
}

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 ohsnap. Review it before you use it.

Capability tags behind 6 rules
  • mcp__ohsnap__check_website untrusted-input, outbound
  • mcp__ohsnap__whoami private-data, untrusted-input
  • mcp__ohsnap__list_monitors untrusted-input
  • mcp__ohsnap__add_monitor untrusted-input, outbound
  • mcp__ohsnap__get_incidents untrusted-input
  • mcp__ohsnap__send_test_alert untrusted-input, 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/io.ohsnap/mcp/verify?hash=e548a0f6e23b0f6a84abdd41068f11259cb6b3136f978c9b19a6d28b9dc4b20f" | jq -e '.changed == false'

Pinned hash e548a0f6e23b, from Nov 10, 2026, 03:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.ohsnap/mcp/changes.xml

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

Badge

Anlyon Radar badge for io.ohsnap/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.ohsnap/mcp.svg)](https://radar.anlyon.com/servers/io.ohsnap/mcp)

Source: MCP Registry · repository. Synced Nov 10, 2026, 03:17 UTC.

OhSnap uptime monitoring MCP server: questions and answers

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

Is the OhSnap uptime monitoring MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 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 OhSnap uptime monitoring MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the OhSnap uptime monitoring MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_test_alert.

What tools does the OhSnap uptime monitoring MCP server have?

6 tools: 1 irreversible, 2 write, 3 read. send_test_alert, check_website, add_monitor, whoami, list_monitors and get_incidents.

Does the OhSnap uptime monitoring MCP server need sign-in or OAuth?

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

Does the OhSnap uptime monitoring 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): check_website, add_monitor and send_test_alert.

Has the OhSnap uptime monitoring MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.