Sitecomb MCP server
com.sitecomb/check-websitesitecomb.comstreamable-httpv1.0.5Scanned
Website quality review: security, privacy, page health, mobile, contact details, found in AI search.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 Sitecomb MCP server can do
The Sitecomb MCP server is published by sitecomb.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_website), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (check_website); 1 tool can send data out of your system (check_website).
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 4 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.0.5.
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 1Claude Code: ask
check_websiteChecks a public website with Sitecomb.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 a public website with Sitecomb. It returns a website quality review: the areas that have problems, with a count for each, and an overall score out of 100. It does not name the problems: those are in the full quality report. Use it when someone asks whether their website is any good, or what is wrong with it. Also use it when someone asks why their website isn't working for them, or asks to check or audit a website. It looks at six areas: Security, Privacy & legal, Page health, Works on phones, Contact details and Found online. A check loads the site the way a visitor's browser does and takes up to about a minute. It only finds problems; it never changes anything on the site. If the site is down or blocks automatic checks, it says it couldn't check and gives no score. Checks are limited per person and per website each day.
Annotations the server declares
- title: Check a website
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 1Show 1 read-only tool
explain_areaExplains what Sitecomb looks at in one of its six areas, by id: security, privacy, quality (page health), phones, customers or ai.No findings
Why it is in this group
- The name "explain_area" says "explain": a word for reading.
Description, as the server wrote it Explains what Sitecomb looks at in one of its six areas, by id: security, privacy, quality (page health), phones, customers or ai. Use it when someone asks what Sitecomb checks, or about an area named in a check_website result. It doesn't check any website.
Annotations the server declares
- title: Explain a Sitecomb area
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- 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 write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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, 18:47 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sitecomb.com/mcp: tools/list returned 2 tools to an anonymous client, including check_website (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.
Tools1 changed.~1 changedView diff
- Changed:check_websiteChanges thingsdescription
Tools1 changed.~1 changedView diff
- Changed:check_websiteChanges thingsdescriptioninputSchema
Tools2 changed.~2 changedView diff
- Changed:check_websiteChanges thingsdescription
- Changed:explain_areaOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:check_websiteChanges thingsdescription
Install
Pinned to version 1.0.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http check-website https://sitecomb.com/mcpclaude mcp add --transport http check-website https://sitecomb.com/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": [
"mcp__check-website__explain_area"
],
"ask": [
"mcp__check-website__check_website"
],
"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 check-website. Review it before you use it.
Capability tags behind 1 rule
- mcp__check-website__check_website 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/com.sitecomb/check-website/verify?hash=358ba962d276122649b3a96ba0d9f7b87725a8ec18d9e9a61e1ad29a05013353" | jq -e '.changed == false'Pinned hash 358ba962d276, from Nov 16, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sitecomb/check-website/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sitecomb/check-website)Source: MCP Registry. Synced Nov 16, 2026, 12:17 UTC.
Sitecomb MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Sitecomb MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 Sitecomb MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Sitecomb 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 Sitecomb MCP server have?
- 2 tools: 1 write, 1 read. check_website and explain_area.
Does the Sitecomb MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Sitecomb MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_website.
Has the Sitecomb MCP server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.