# OhSnap uptime monitoring (remote · mcp.ohsnap.io)

Check if a website is down, add uptime monitors, read outage history and send test alerts.

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.ohsnap.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-ohsnap-mcp/mcp.md), [page](https://verifymcp.io/servers/io-ohsnap-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.ohsnap.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 692 tokens (~115/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-ohsnap-mcp 'https://mcp.ohsnap.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-ohsnap-mcp": {
      "url": "https://mcp.ohsnap.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-ohsnap-mcp": {
      "type": "http",
      "url": "https://mcp.ohsnap.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-ohsnap-mcp]
url = "https://mcp.ohsnap.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-ohsnap-mcp": {
      "type": "remote",
      "url": "https://mcp.ohsnap.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-ohsnap-mcp --url 'https://mcp.ohsnap.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-ohsnap-mcp:
    url: "https://mcp.ohsnap.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-ohsnap-mcp": {
      "Transport": "http",
      "Url": "https://mcp.ohsnap.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-ohsnap-mcp -t streamable-http -u 'https://mcp.ohsnap.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-ohsnap-mcp": {
      "type": "http",
      "url": "https://mcp.ohsnap.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, +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.

### 2026-11-03 (score 77, +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.

### 2026-11-01 (score 76, +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.

### 2026-10-30 (score 75, +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.

### 2026-10-28 (score 74, +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.

### 2026-10-27 (score 73, 0)

- [security] 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
- [cosmetic] “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

### 2026-10-25 (score 73, +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.

### 2026-10-23 (score 72, +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.

## MCP tools (6)

### `check_website` (~129 tokens)

Check if a website is up

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.

Input parameters:

- `url` (string, required): Website URL or bare domain, e.g. "example.com" or "https://example.com/shop".

### `whoami` (~51 tokens)

Show the connected OhSnap account

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.

### `list_monitors` (~58 tokens)

List monitored websites

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.

### `add_monitor` (~177 tokens)

Start monitoring a website

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.

Input parameters:

- `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, required): Website URL or bare domain to monitor.

### `get_incidents` (~106 tokens)

Get outage history for a website

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.

Input parameters:

- `days` (integer): How far back to look. Default 30, max 90.
- `limit` (integer): Maximum incidents to return. Default 10.
- `website_id` (string, required): Website id from list_monitors or add_monitor.

### `send_test_alert` (~71 tokens)

Send a test alert

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.

Input parameters:

- `website_id` (string, required): Website id from list_monitors or add_monitor.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-ohsnap-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.ohsnap.io/mcp
- Website: https://ohsnap.io/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/io-ohsnap-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-ohsnap-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-ohsnap-mcp/mcp