OhSnap uptime monitoring
REMOTE · MCP.OHSNAP.IO
Check if a website is down, add uptime monitors, read outage history and send test alerts.
Available components
Last scanned (5 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 692 tokens (~115/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Tool “add_monitor” rewrote its description, which is the text the model reads security
- Tool “send_test_alert” rewrote its description, which is the text the model reads security
- “get_incidents” reworded the description of “website_id” cosmetic
- “send_test_alert” reworded the description of “website_id” cosmetic
- Tool “get_incidents” changed its title: Get outage history for a monitor → Get outage history for a website cosmetic
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.ohsnap.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ohsnap.io | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 55f986cc5d3f9bc913d71482b2148805 |
| SANs: ohsnap.io, mcp.ohsnap.io, *.mcp.ohsnap.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ohsnap.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| ohsnap.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ohsnap.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ohsnap.io/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_monitor Start monitoring a website ~177
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 website will run silently. SMS, WhatsApp, Slack and Telegram alerts are configured in the OhSnap dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_email | string | – | Email address for down/up alerts. Used only if the account has no email alert channel yet. |
| check_frequency_seconds | integer | – | Seconds between checks. Raised to the plan minimum (300 on Free, 30 on Unlimited). Defaults to 300. |
| name | string | – | Display name. Defaults to the hostname. |
| url | string | yes | Website URL or bare domain to monitor. |
No output schema declared.
No examples provided.
check_website Check if a website is up ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or bare domain, e.g. "example.com" or "https://example.com/shop". |
No output schema declared.
No examples provided.
get_incidents Get outage history for a website ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far back to look. Default 30, max 90. |
| limit | integer | – | Maximum incidents to return. Default 10. |
| website_id | string | yes | Website id from list_monitors or add_monitor. |
No output schema declared.
No examples provided.
list_monitors List monitored websites ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_test_alert Send a test alert ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| website_id | string | yes | Website id from list_monitors or add_monitor. |
No output schema declared.
No examples provided.
whoami Show the connected OhSnap account ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the OhSnap uptime monitoring MCP server?
OhSnap uptime monitoring is a hosted endpoint at https://mcp.ohsnap.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ohsnap.io
claude mcp add --transport http io-ohsnap-mcp 'https://mcp.ohsnap.io/mcp'
What is the OhSnap uptime monitoring MCP server?
OhSnap uptime monitoring is an MCP server listed in the public MCP registry as io.ohsnap/mcp. Check if a website is down, add uptime monitors, read outage history and send test alerts. This page covers its hosted endpoint (https://mcp.ohsnap.io/mcp).
Is the OhSnap uptime monitoring MCP server safe to use?
OhSnap uptime monitoring scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OhSnap uptime monitoring MCP server expose?
OhSnap uptime monitoring exposes 6 tools: check_website, whoami, list_monitors, add_monitor, get_incidents, send_test_alert. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.
Does the OhSnap uptime monitoring MCP server require authentication?
No. We connected to OhSnap uptime monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OhSnap uptime monitoring MCP server still maintained?
OhSnap uptime monitoring is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.