Zovo Website Status Checker MCP server
io.github.theluckystrike/site-statustheluckystrikestreamable-httpv1.0.0Scanned
Is it down, or just you?
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 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 Zovo Website Status Checker MCP server can do
The Zovo Website Status Checker MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (2 tools: check_websites and check_security_headers), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (check_websites and check_security_headers); 2 tools can send data out of your system (check_websites and check_security_headers).
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 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.
2 tools
Changes things 2Claude Code: ask
check_security_headersChecks one public URL from the Zovo edge network and reports the six key security headers with an A-F grade, HTTP status, verdict, response time, TLS, robots.txt and a CSV download…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 Checks one public URL from the Zovo edge network and reports the six key security headers with an A-F grade, HTTP status, verdict, response time, TLS, robots.txt and a CSV download. The headers are Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options or frame-ancestors, Referrer-Policy and Permissions-Policy. Use for a current security-header review. It cannot check zovo.one sites, IP literals, private or reserved addresses, or ports other than 80 and 443. Do not use for vulnerability testing, continuous monitoring or more than one site.
Annotations the server declares
- title: Check security headers
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
check_websitesMakes live requests from the Zovo edge network to up to 10 public URLs and reports each verdict, redirect chain, HTTP status, response time, TLS, page title and security headers, p…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 Makes live requests from the Zovo edge network to up to 10 public URLs and reports each verdict, redirect chain, HTTP status, response time, TLS, page title and security headers, plus a CSV download. Use for a current availability, redirect or status check. It cannot check zovo.one or its subdomains, IP literals, private or reserved addresses, or ports other than 80 and 443. Sites can block automated checks. Do not use for monitoring or uptime history.
Annotations the server declares
- title: Check websites
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
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 out2
- 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 20, 2026, 19:35 UTC, unchanged since Oct 22, 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://site-status.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including check_websites (write), check_security_headers (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.
Tools2 changed.~2 changedView diff
- Changed:check_security_headersChanges thingsdescription
- Changed:check_websitesChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http site-status https://site-status.zovo.one/mcpclaude mcp add --transport http site-status https://site-status.zovo.one/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__site-status__check_websites",
"mcp__site-status__check_security_headers"
],
"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 site-status. Review it before you use it.
Capability tags behind 2 rules
- mcp__site-status__check_websites untrusted-input, outbound
- mcp__site-status__check_security_headers untrusted-input, 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/io.github.theluckystrike/site-status/verify?hash=0bf69c6d1c9da33adadd7cc910c841a3fe7420af5fceb031eaec8b68eb56a654" | jq -e '.changed == false'Pinned hash 0bf69c6d1c9d, from Nov 8, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/site-status/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/site-status)Source: MCP Registry. Synced Oct 22, 2026, 06:20 UTC.
Zovo Website Status Checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Website Status Checker MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 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 Zovo Website Status 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 Zovo Website Status 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 Zovo Website Status Checker MCP server have?
- 2 tools: 2 write. check_websites and check_security_headers.
Does the Zovo Website Status Checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Website Status Checker MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_websites and check_security_headers.
Has the Zovo Website Status Checker MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.