List your agent

Sites in the Woods

MCP server● Hosted · onlineInstallablev0.2.1

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

Reviews

No review yet. Used Sites in the Woods? Be the first to help others choose.

What it does

Sites in the Woods is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version0.2.1
Packagesnpm
PriceNot in the registry
First seen19 Nov 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://sitesinthewoods.com/mcp streamable-http

In Claude Code: claude mcp add --transport http sites-in-the-woods https://sitesinthewoods.com/mcp

Install package

  • NPM sites-in-the-woods v0.1.0 · runs locally (stdio)

Required: SITES_IN_THE_WOODS_API_KEY (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "sites-in-the-woods": {
      "url": "https://sitesinthewoods.com/mcp"
    }
  }
}

Reliability

Re-tested about every 3 days · last check 1d ago
Insufficient observations1 conclusive check in 30 days; a figure is shown from 10
1 / 0Answers / failures, 30 days
No key neededAccess status (latest answer)
Observed test history · one mark = one check
19 Nov19 Nov
AnsweredAnswered, key requiredNo valid answer

Observed endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 19 Nov 2026). How we measure

Tool changes

Tool tracking since 20 Nov 2026 · test history since 19 Nov 2026

No tool added or removed since tracking started. 18 tools in the latest list.

Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Sites in the Woods answered an MCP connection on 19 Nov 2026 and introduced itself as sites-in-the-woods 0.2.1 (MCP protocol 2025-06-18).

18 tools offered to AI assistants

  • status · 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.
  • sites · 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.
  • sites_by_slug · 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 cer
  • sites_by_slug_insights · 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'
  • sites_by_slug_scans · 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 w
  • sites_by_slug_scans_by_id · 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
  • sites_by_slug_maintenance · 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 n
  • sites_by_slug_map · 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 re
  • sites_by_slug_events · 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, new
  • incidents · 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 slowdow
  • domains · 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.
  • incidents_by_id_dismiss · 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 tea
Show 6 more
  • incidents_by_id_undismiss · 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.
  • incidents_by_id_recheck · 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 who
  • sites_by_slug_maintenance_start · 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 wh
  • sites_by_slug_maintenance_end · 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
  • sites_by_slug_pause · 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
  • sites_by_slug_resume · 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.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install packagesites-in-the-woodsDECLAREDSRC-001 Official MCP Registry1d ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry1d ago
Version0.2.1DECLAREDSRC-001 Official MCP Registry1d ago
Hosted endpointhttps://sitesinthewoods.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://sitesinthewoods.comDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

  • CHANGED19 Nov 2026
    local install: no → yes
  • VERSION19 Nov 2026
    0.2.0 → 0.2.1
  • NEW19 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Sites in the Woods? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Sites in the WoodsLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Sites in the Woods?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/sites-in-the-woods?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/sites-in-the-woods/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Sites in the Woods

How do I connect Sites in the Woods?

Use the hosted endpoint https://sitesinthewoods.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Sites in the Woods need an API key or token?

Yes. The registry entry lists a required value: SITES_IN_THE_WOODS_API_KEY. Get it from the publisher.

What tools does Sites in the Woods offer?

When Electra Index connected on 19 Nov 2026, it listed 18 tools: status, 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 more. The full list is in "Live check" above.

Is Sites in the Woods online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.