UpLane Website Uptime Checker MCP server
dev.workers.deanhiki.uplane/website-uptimeuplane.deanhiki.workers.devstreamable-httpv1.0.0Scanned
Check if any website is up (status, latency, redirects, security headers) and set uptime alerts.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the UpLane Website Uptime Checker MCP server can do
The UpLane Website Uptime Checker MCP server is published by uplane.deanhiki.workers.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: check_website, check_websites and start_uptime_monitor), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (check_website and check_websites); 3 tools can send data out of your system (check_website, check_websites and start_uptime_monitor).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
check_websiteCheck 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 secur…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
check_websitesCheck up to 10 URLs in parallel and get up/down, HTTP status and response time for each.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Check up to 10 URLs in parallel and get up/down, HTTP status and response time for each. Free, no key.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
start_uptime_monitorMonitor 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.Can send data outNo findings
Why it is in this group
- The name "start_uptime_monitor" says "start": a word for a change.
What it can reach
- outboundThe input takes a destination (input.chat_id): what the tool writes goes there.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:23 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://uplane.deanhiki.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including check_website (write), check_websites (write), start_uptime_monitor (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http website-uptime https://uplane.deanhiki.workers.dev/mcpclaude mcp add --transport http website-uptime https://uplane.deanhiki.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__website-uptime__check_website",
"mcp__website-uptime__check_websites",
"mcp__website-uptime__start_uptime_monitor"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as website-uptime. Review it before you use it.
Capability tags behind 3 rules
- mcp__website-uptime__check_website untrusted-input, outbound
- mcp__website-uptime__check_websites untrusted-input, outbound
- mcp__website-uptime__start_uptime_monitor outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.deanhiki.uplane/website-uptime/verify?hash=7b4d579beac75527dcf167c2741d1f0136286c9af78b1074da7dd8e93e3d89c0" | jq -e '.changed == false'Pinned hash 7b4d579beac7, from Nov 13, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.deanhiki.uplane/website-uptime/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.deanhiki.uplane/website-uptime)Source: MCP Registry. Synced Oct 31, 2026, 23:17 UTC.
UpLane Website Uptime Checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the UpLane Website Uptime Checker MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the UpLane Website Uptime Checker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the UpLane Website Uptime Checker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the UpLane Website Uptime Checker MCP server have?
- 3 tools: 3 write. check_website, check_websites and start_uptime_monitor.
Does the UpLane Website Uptime Checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the UpLane Website Uptime Checker MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_website, check_websites and start_uptime_monitor.
Has the UpLane Website Uptime Checker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.