OhSnap uptime monitoring MCP server

• add_monitorFree

  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; Unlimited allows any number every 30 seconds. Pass alert_email if the account has no alert channel yet, otherwise the monitor will run silently. SMS, WhatsApp, Slack and Telegram alerts are configured in the OhSnap dashboard.

• check_websiteFree

  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.

• get_incidentsFree

  Returns recent outages for one monitored website: when each started and ended, how long it lasted, and the error. On the Unlimited plan each incident includes an AI diagnosis in plain language; on Free it is marked ai_locked.

• list_monitorsFree

  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.

• send_test_alertwrite actionFree

  Sends a clearly labelled test DOWN alert through every alert channel linked to a monitor (email, SMS, WhatsApp, Slack, Telegram), so the user can confirm alerts reach them. Limited to one test per monitor per minute.

• whoamiFree

  Returns the OhSnap account this MCP key belongs to: email, plan (Free, Unlimited, Agency), the monitor cap, and the fastest allowed check interval. Call before add_monitor to explain plan limits up front.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 766ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenanceno repository listed3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

72/100

higher than 37% of 48,243 servers

Tools

6

the typical server has 7

Tools that change things

17%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

120 ms

faster than 80% of 30,027 servers

OhSnap uptime monitoring: common questions

Is OhSnap uptime monitoring MCP server safe?

Mostly: it is graded B (72/100). Read the OhSnap uptime monitoring safety report

How do I install OhSnap uptime monitoring?

It runs remotely at mcp.ohsnap.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does OhSnap uptime monitoring need an API key?

Yes. The registry entry asks for Authorization.

Is OhSnap uptime monitoring maintained?

The latest release is v1.0.0.

Is OhSnap uptime monitoring up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of OhSnap uptime monitoring?

Servers from other publishers that do the same job: Netdata MCP server, OneUptime MCP server and Domain Liveness MCP server.

How does OhSnap uptime monitoring compare with other MCP servers?

safety score 72/100 (higher than 37% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.