Check if any website is up (status, latency, redirects, security headers) and set uptime alerts.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Check right now whether a website/URL is up: HTTP status, response time (ms) from Cloudflare's edge, redirect chain and final URL, content type/size, server header, and which security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) are present or missing. Free, no key.
Full http(s) URL, e.g. https://example.com
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http website-uptime https://uplane.deanhiki.workers.dev/mcp
Check right now whether a website/URL is up: HTTP status, response time (ms) from Cloudflare's edge, redirect chain and final URL, content type/size, server header, and which security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) are present or missing. Free, no key.
| Argument | Type | Description |
|---|---|---|
| url* | string | Full http(s) URL, e.g. https://example.com |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Full http(s) URL, e.g. https://example.com"
}
}
}Check up to 10 URLs in parallel and get up/down, HTTP status and response time for each. Free, no key.
| Argument | Type | Description |
|---|---|---|
| urls* | array |
{
"type": "object",
"required": [
"urls"
],
"properties": {
"urls": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 10
}
}
}Monitor up to 3 URLs every ~5 minutes and send DOWN/UP alerts to a Slack or Discord webhook or a Telegram bot, plus a public status page. Free 7-day trial, no signup. UpLane Pro: 50 URLs, 7 USDC/month (key UP-... from https://uplane.deanhiki.workers.dev/#pro).
| Argument | Type | Description |
|---|---|---|
| name | string | Status page name |
| urls* | array | |
| chat_id | string | Telegram chat_id (Telegram only) |
| pro_key | string | |
| webhook* | string | Slack/Discord webhook URL or https://api.telegram.org/bot<token>/sendMessage |
{
"type": "object",
"required": [
"urls",
"webhook"
],
"properties": {
"name": {
"type": "string",
"description": "Status page name"
},
"urls": {
"type": "array",
"items": {
"type": "string"
}
},
"chat_id": {
"type": "string",
"description": "Telegram chat_id (Telegram only)"
},
"pro_key": {
"type": "string"
},
"webhook": {
"type": "string",
"description": "Slack/Discord webhook URL or https://api.telegram.org/bot<token>/sendMessage"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Oct 31, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.