Your team's website monitoring: uptime, incidents, speed, TLS and domain expiry.
MCP Score How we grade
From what our daily checks can see without credentials, last checked 21 Nov 2026.
| Reliability Answered 3 of 3 daily checks. |
30 / 30 |
| Speed Typical response 326 ms. |
12 / 20 |
| Tool docs 26 of 26 tools have a full description; 45 of 45 inputs have a description. |
25 / 25 |
| Stability 2 tool rewrites in 30 days (description or inputs changed, or removed). |
10 / 15 |
| Listing Complete registry listing. |
10 / 10 |
How to raise the grade
- Answer initialize faster: under 150 ms earns full Speed points (yours: 326 ms).
- Change tool descriptions and inputs rarely, and with a new version: agents trust stable tools.
Connect Remote server
claude mcp add --transport http monitor https://sitesinthewoods.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"monitor": {
"url": "https://sitesinthewoods.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"monitor": {
"type": "http",
"url": "https://sitesinthewoods.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://sitesinthewoods.com/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 26 found in our last check
statusWraps 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.
sitesWraps 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_slugWraps 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.
sites_by_slug_insightsWraps 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…
sites_by_slug_scansWraps 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)…
sites_by_slug_scans_by_idWraps 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 agen…
sites_by_slug_maintenanceWraps 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 th…
sites_by_slug_mapWraps 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 f…
sites_by_slug_eventsWraps 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 dashboar…
incidentsWraps 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.
incidents_by_idWraps GET /api/incidents/{id}. One incident in full: an outage's whole diagnosis, where it was seen and how it failed. Call this for the story of one incident, open or resolved: the likely cause, every clue, which locations saw it, what the other location said, how the checks fa…
domainsWraps 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.
public_sitesWraps GET /api/public/sites. Every public site's status and uptime, no key needed. Call this to see the public status pages' sites right now, without a key: each one's status, typical response time and uptime, as the status page shows them.
public_sites_by_slugWraps GET /api/public/sites/{slug}. One public site's 90 days: daily uptime, response time and outages, no key needed. Call this for a public site's history without a key: uptime over 1, 7, 30 and 90 days, one row per day and every outage, the same numbers as its status page (CC…
incidents_by_id_dismissWraps 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 te…
incidents_by_id_undismissWraps 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_recheckWraps 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, o…
sites_by_slug_maintenance_startWraps 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…
sites_by_slug_maintenance_endWraps 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…
sites_by_slug_pauseWraps 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.
sites_by_slug_resumeWraps 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.
sites_by_slug_journeysWraps GET /api/sites/{slug}/journeys. A site's agent journeys: what each asks an agent to do, its model and schedule, and its latest verdict. Call this to see how agents fare on the site: each journey is a Claude agent sent to do one job (sign up, find an answer) on a schedule.…
sites_by_slug_journeys_by_journey_runsWraps GET /api/sites/{slug}/journeys/{journey}/runs. A journey's runs, newest first: verdicts, where they got stuck, costs and outcome checks. Call this to see how a journey has gone lately (the last 90 days), and to pick a run to read step by step. A comparison of models' runs…
sites_by_slug_journeys_by_journey_runs_by_idWraps GET /api/sites/{slug}/journeys/{journey}/runs/{id}. One journey run, step by step: what the agent thought, fetched, got back and why it stopped. Call this to see exactly what an agent met on the site: each request with its status and time, how the agent found the URL, what…
sites_by_slug_journeys_by_journey_runWraps POST /api/sites/{slug}/journeys/{journey}/run. Run a journey now, as a job. Queues one run of the journey on its own model, as the journey page's Run now does; the monitor starts it within a minute and a run takes from 15 seconds to a few minutes. Answers 202 with `Locatio…
sites_by_slug_journeys_by_journey_requests_by_idWraps GET /api/sites/{slug}/journeys/{journey}/requests/{id}. A journey run asked for with Run now: queued, running or finished, and its verdict. Poll this after asking for a run (every few seconds, as Retry-After says): `status` goes from queued to running to finished, and `run…
Tool changes seen by our daily check
20 Nov 2026Added:
incidents_by_id,public_sites,public_sites_by_slug,sites_by_slug_journeys,sites_by_slug_journeys_by_journey_requests_by_id,sites_by_slug_journeys_by_journey_run,sites_by_slug_journeys_by_journey_runs,sites_by_slug_journeys_by_journey_runs_by_id. Inputs changed:incidents,sites.
Renames and new inputs are usually routine. A changed description changes what your agent is told the tool does, and can carry new instructions: review it before you rely on the tool again.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Bearer sm_…: an API key from the team's API keys page (viewer keys read; member and admin keys also write). Listing the tools needs none. |
Details
| Endpoint | https://sitesinthewoods.com/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| First published | 19 Nov 2026 |
| Last updated | 19 Nov 2026 |
| Registry name | com.sitesinthewoods/monitor |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
