Skip to content

Sites in the Woods MCP server

com.sitesinthewoods/monitorsitesinthewoods.comstreamable-httpv0.2.1Scanned

Your team's website monitoring: uptime, incidents, speed, TLS and domain expiry.

18 tools: 1 can delete or cancel things, 16 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 16 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Sites in the Woods MCP server can do

The Sites in the Woods MCP server is published by sitesinthewoods.com, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (1 tool: sites_by_slug_pause) and create or change data (16 tools: sites, sites_by_slug, sites_by_slug_insights, sites_by_slug_scans and 12 more). 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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 19, 2026, version 0.2.1.

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.

18 tools

Deletes or cancels 1Claude Code: deny
  • sites_by_slug_pauseWraps POST /api/sites/{slug}/pause.No 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 destructive (destructiveHint: true).
    Description, as the server wrote it
    Wraps POST /api/sites/{slug}/pause. Pause a site's checks. Stops every check of the site, keeping its history, until it's resumed. Nothing alerts while it's paused. It acts for the whole team. Needs an Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Pause a site's checks
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 16Claude Code: ask
  • domainsWraps GET /api/domains.No 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.
    Description, as the server wrote it
    Wraps GET /api/domains. The team's domains: registration expiry, registrar, nameservers, status. Call this to check renewals: which domains expire soon, who the registrar is, and whether nameservers or registry locks changed.

    Annotations the server declares

    • title: The team's domains: registration expiry, registrar, nameservers, status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • incidentsWraps GET /api/incidents.No 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.
    Description, as the server wrote it
    Wraps GET /api/incidents. Incidents, open now or recent; open outages and slowdowns carry the likely cause. Call this to see what went wrong and why: open and recent incidents, newest first, with the likely cause on open outages and slowdowns. Page through with limit and offset.

    Annotations the server declares

    • title: Incidents, open now or recent; open outages and slowdowns carry the likely cause
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • incidents_by_id_dismissWraps POST /api/incidents/{id}/dismiss.No findings

    Why it is in this group

    • The name "incidents_by_id_dismiss" says "dismiss": a word for a change.
    Description, as the server wrote it
    Wraps POST /api/incidents/{id}/dismiss. Dismiss an open incident as noise. Hides it from the open lists for the whole team; it never alerts again and closes without a message. Not every kind can be dismissed (409). It acts for the whole team. Needs a Member or Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Dismiss an open incident as noise
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • incidents_by_id_recheckWraps POST /api/incidents/{id}/recheck.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Wraps POST /api/incidents/{id}/recheck. Check an incident again now. The monitor checks it again within 30 seconds, after a fix, instead of waiting for the next scheduled check. Not every kind can be checked again (409). It acts for the whole team. Needs a Member or Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Check an incident again now
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • incidents_by_id_undismissWraps POST /api/incidents/{id}/undismiss.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Wraps POST /api/incidents/{id}/undismiss. Bring back a dismissed incident. Undoes a dismiss: the incident shows and alerts again. It acts for the whole team. Needs a Member or Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Bring back a dismissed incident
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sitesWraps GET /api/sites.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites. The team's sites: status, homepage uptime over 1, 7 and 30 days, open incidents. Call this to compare sites or report on uptime over the last day, week or month. It also lists the slugs every other route takes.

    Annotations the server declares

    • title: The team's sites: status, homepage uptime over 1, 7 and 30 days, open incidents
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slugWraps GET /api/sites/{slug}.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}. One site: its last 7 days (as in the weekly brief), open incidents, domain and TLS expiry. Call this to answer questions about one site: how it did this week, what's wrong with it now, and when its domain or certificate runs out.

    Annotations the server declares

    • title: One site: its last 7 days (as in the weekly brief), open incidents, domain and TLS expiry
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_eventsWraps GET /api/sites/{slug}/events.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/events. What changed on one site: incidents opened and resolved, code pushes, maintenance, new pages. Call this to find what changed before a number moved (clicks fell, pages got slower): the site's timeline, newest first, the same events the dashboard draws on its charts. Page through with limit and offset.

    Annotations the server declares

    • title: What changed on one site: incidents opened and resolved, code pushes, maintenance, new pages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_insightsWraps GET /api/sites/{slug}/insights.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/insights. One site's daily insights: page weight, security headers, prefetches, page errors, broken links, cache, dead ends. Call this when a site is slow or heavy, or to find what to fix: the daily browser load's page weight, missing security headers, JavaScript errors and broken links.

    Annotations the server declares

    • title: One site's daily insights: page weight, security headers, prefetches, page errors, broken links, cache, dead ends
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_maintenanceWraps GET /api/sites/{slug}/maintenance.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/maintenance. One site's maintenance windows: on now, scheduled, and the last 30 days. Call this to see whether a site is in a maintenance window (its alerts held, its uptime not counting that time) and when the next one is. Windows are started from the dashboard or a deploy calling the site's maintenance URL (POST <url>/start?minutes=30, POST <url>/end), which the dashboard shows to admins.

    Annotations the server declares

    • title: One site's maintenance windows: on now, scheduled, and the last 30 days
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_maintenance_endWraps POST /api/sites/{slug}/maintenance/end.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Wraps POST /api/sites/{slug}/maintenance/end. End a site's maintenance windows now. Call this after a deploy: alerts for the site go out again from now. Ending with no window on answers `ended: 0`. It acts for the whole team. Needs a Member or Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: End a site's maintenance windows now
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_maintenance_startWraps POST /api/sites/{slug}/maintenance/start.No findings

    Why it is in this group

    • The name "sites_by_slug_maintenance_start" says "start": a word for a change.
    Description, as the server wrote it
    Wraps POST /api/sites/{slug}/maintenance/start. Start a maintenance window on a site now. Call this before a deploy: alerts for the site are held (checks still run) until the window ends, after `minutes` (default 30, at most 24 hours) or when you end it. Starting again replaces the open window. It acts for the whole team. Needs a Member or Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Start a maintenance window on a site now
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_mapWraps GET /api/sites/{slug}/map.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/map. One site's structure from its sitemaps: sections, new and removed pages, what fails. Call this to see where a site is changing or breaking without crawling it: every path with pages under it, with new and removed pages in the window, pages that fail, broken links and sitemaps that miss pages. Add ?section= for one section's pages. Our sites only (competitors' sitemaps aren't read).

    Annotations the server declares

    • title: One site's structure from its sitemaps: sections, new and removed pages, what fails
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_resumeWraps POST /api/sites/{slug}/resume.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Wraps POST /api/sites/{slug}/resume. Resume a paused site's checks. Starts the site's checks again within a minute. It acts for the whole team. Needs an Admin key, on a team with 10 sites or more.

    Annotations the server declares

    • title: Resume a paused site's checks
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_scansWraps GET /api/sites/{slug}/scans.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/scans. One site's API recovery scans, newest first: state, how each ended, and findings by weight. Call this to see whether a site has been scanned for dead ends (API errors that don't say how to recover, lists without paging, pages nothing links to) and how the last scan came out. Scans are started from the dashboard by an admin or owner.

    Annotations the server declares

    • title: One site's API recovery scans, newest first: state, how each ended, and findings by weight
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • sites_by_slug_scans_by_idWraps GET /api/sites/{slug}/scans/{id}.No 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.
    Description, as the server wrote it
    Wraps GET /api/sites/{slug}/scans/{id}. One API recovery scan: what it saw, its findings, the fixes and what changed since the last scan. Call this for a scan's results: findings by weight with the places on the site, three to five fixes in words and as a block for a coding agent, and new, fixed and still-open findings since the previous scan. It never includes text from the scanned site.

    Annotations the server declares

    • title: One API recovery scan: what it saw, its findings, the fixes and what changed since the last scan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • statusWraps GET /api/status.No findings

    Why it is in this group

    • The name "status" says "status": a word for reading.
    Description, as the server wrote it
    Wraps GET /api/status. Every one of the team's sites: its status right now, and the open incidents. Call this first, or on a schedule (at most once a minute, as often as the checks run), to see whether anything is down or warning right now.

    Annotations the server declares

    • title: Every one of the team's sites: its status right now, and the open incidents
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 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
25
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 25 tools that change things (1 destructive, 24 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sitesinthewoods.com/mcp: tools/list returned 26 tools to an anonymous client, including sites_by_slug_pause (destructive), sites (write), sites_by_slug (write), sites_by_slug_insights (write), sites_by_slug_scans (write) and 20 more

    What this check looks for

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 0.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http monitor https://sitesinthewoods.com/mcp
claude mcp add --transport http monitor https://sitesinthewoods.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__monitor__status"
    ],
    "ask": [
      "mcp__monitor__sites",
      "mcp__monitor__sites_by_slug",
      "mcp__monitor__sites_by_slug_insights",
      "mcp__monitor__sites_by_slug_scans",
      "mcp__monitor__sites_by_slug_scans_by_id",
      "mcp__monitor__sites_by_slug_maintenance",
      "mcp__monitor__sites_by_slug_map",
      "mcp__monitor__sites_by_slug_events",
      "mcp__monitor__incidents",
      "mcp__monitor__domains",
      "mcp__monitor__incidents_by_id_dismiss",
      "mcp__monitor__incidents_by_id_undismiss",
      "mcp__monitor__incidents_by_id_recheck",
      "mcp__monitor__sites_by_slug_maintenance_start",
      "mcp__monitor__sites_by_slug_maintenance_end",
      "mcp__monitor__sites_by_slug_resume"
    ],
    "deny": [
      "mcp__monitor__sites_by_slug_pause"
    ]
  }
}

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 monitor. Review it before you use it.

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.sitesinthewoods/monitor/verify?hash=3cd68dc63fb971d27a24a06614ededc1a8098350dd82991dd7c6cb417da5727b" | jq -e '.changed == false'

Pinned hash 3cd68dc63fb9, from Nov 19, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.sitesinthewoods/monitor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.sitesinthewoods/monitor
[![Anlyon Radar](https://radar.anlyon.com/badge/com.sitesinthewoods/monitor.svg)](https://radar.anlyon.com/servers/com.sitesinthewoods/monitor)

Source: MCP Registry. Synced Nov 19, 2026, 20:17 UTC.

Sites in the Woods MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Sites in the Woods MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 17 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 Sites in the Woods MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: sites_by_slug_pause.

Can the Sites in the Woods 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 Sites in the Woods MCP server have?

18 tools: 1 destructive, 16 write, 1 read. sites_by_slug_pause, sites, sites_by_slug, sites_by_slug_insights, sites_by_slug_scans, sites_by_slug_scans_by_id, sites_by_slug_maintenance, sites_by_slug_map and 10 more.

Does the Sites in the Woods MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Sites in the Woods MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Sites in the Woods MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.