Lets an assistant check whether a website is down and manage OhSnap uptime monitors, outage history, and test alerts.
What you can do
This remote MCP server connects an assistant to OhSnap uptime monitoring. It can check whether a website is currently down, add new uptime monitors, read outage history, and send test alerts. Tools are not enumerated in the supplied manifest, so the exact tool set beyond these described actions is not documented here.
When to use it
Useful when you want an assistant to verify site availability during troubleshooting, set up or review uptime monitoring, or trigger a test alert to confirm notifications work. It fits operations and on-call workflows where quick availability checks are needed.
Requirements
A remote streamable HTTP endpoint at mcp.ohsnap.io; no local runtime or package is needed. An Authorization header carrying a bearer key from the OhSnap connect page is required for most actions, though the website check is described as working without it.
Before you install
The Authorization header carries a secret bearer key; treat it as a credential and avoid exposing it in logs or shared transcripts. Adding monitors and sending test alerts change state or send notifications, so confirm before running them. The service is third-party and receives the website addresses and account data you submit.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.ohsnap%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersurlrequired
whoami
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.
Takes no parameters.
list_monitors
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.
Takes no parameters.
add_monitor
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 monitor will run silently. SMS, WhatsApp, Slack and Telegram alerts are configured in the OhSnap dashboard.
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.
Parametersdayslimitwebsite_idrequired
send_test_alert
Send a test alert
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.
Parameterswebsite_idrequired
Version history
1
v1.0.0LatestOct 14, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.