Sentinel Monitoring

Uptime, SSL, DNS and domain monitoring you can talk to — check, create and manage monitors for all your client sites from Claude or any MCP client.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Get Uptime Summary Tool: Returns an at-a-glance uptime summary for the user's current team: how many monitors are up, down, or paused, plus the monitors currently down and any open incidents. Use this
  • Get Attention Items Tool: Returns a prioritized list of everything in the user's current team that needs attention right now — monitors that are down or degraded, SSL certificates and domains expiring
  • List Monitors Tool: Lists the uptime monitors in the user's current team. By default each row is compact (id, url, status, 7-day avg response time) so large teams fit in one response; pass verbose=tru

What data it sees

Do you need an account

No: the server works without sign-in

Uptime, SSL, DNS and domain monitoring you can talk to — check, create and manage monitors for all your client sites from Claude or any MCP client. Built for agencies and freelancers managing client websites: ask "which client SSL certificates expire this month?", "what was uptime across all sites in June?", or "add monitoring for newclient.com" in plain language. Tools cover monitors, incidents, on-demand URL checks from every region, uptime summaries, DNS and performance history, expiring-certificate reports, status pages, and a needs-attention digest. Hosted remote server with OAuth — nothing to install. Requires a paid Sentinel plan (reads from Starter, writes on Pro/Business). Docs: https://sentinel.rootstuff.io/docs/mcp · GitHub: https://github.com/rootstuff/sentinel-mcp

How to connect

How to connect Sentinel Monitoring to Claude

The server address to paste into Claude settings:

https://sentinel-monitoring--adam-z5fq.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Sentinel Monitoring to ChatGPT

The server address to paste into ChatGPT settings:

https://sentinel-monitoring--adam-z5fq.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Sentinel Monitoring to Cursor

The server address to paste into Cursor settings:

https://sentinel-monitoring--adam-z5fq.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (21)

Raw names from tools/list. Only developers need these.

get-uptime-summary-toolReturns an at-a-glance uptime summary for the user's current team: how many monitors are up, down, or paused, plus the monitors currently down and any open incidents. Use this to answer "is anything down right now?".
get-attention-items-toolReturns a prioritized list of everything in the user's current team that needs attention right now — monitors that are down or degraded, SSL certificates and domains expiring soon, response-time regressions, and open incidents. Use this to answer "what needs my attention?" or "anything I should know this morning?".
list-monitors-toolLists the uptime monitors in the user's current team. By default each row is compact (id, url, status, 7-day avg response time) so large teams fit in one response; pass verbose=true for name, type, check interval, and last-checked time. Supports search/status/type filters and sort="response_time" (slowest first). Paginated: use offset with has_more/next_offset to page. Prefer filters and the compact default to keep responses small.
get-monitor-toolGets details for a single monitor in the user's current team, including the latest response time per region and recent incidents.
list-incidents-toolLists incidents (outages) for the user's current team, newest first. Supports optional filters by monitor, status, and date range. Paginated: pass offset to page through history and use has_more/next_offset to fetch the rest.
list-status-pages-toolLists the public status pages enabled for the user's current team, including each page's slug, custom domain, and the status of its underlying monitor.
list-expiring-certificates-toolLists SSL certificates and/or domain registrations in the user's current team that expire within a given window, soonest first. Answers questions like "any SSL certificates expiring soon?" or "which domains renew this month?".
get-performance-history-toolReturns performance history for a monitor in the user's current team: daily response-time trend (avg/min/max + DNS/TCP/TLS/TTFB phases) and Lighthouse score history (performance/accessibility/SEO/best-practices + Core Web Vitals) per strategy.
get-dns-history-toolReturns the DNS snapshot history for a monitor in the user's current team — the timeline of recorded DNS records per type (newest first), which reveals when records changed. The baseline snapshot is flagged.
check-url-toolProbe a URL right now from Sentinel's global monitoring regions and return per-region reachability and latency. Use this to verify an endpoint is actually up worldwide — something an agent cannot do from a single location. This is a one-shot check: it does not create a monitor or store history, and a single probe is noisier than ongoing monitoring (a transient blip can read as offline).
create-monitor-toolCreates a new monitor in the user's current team. Requires full API access (Pro/Business). The monitor type must be supported by the plan; check_types are filtered to those valid for the type.
update-monitor-toolUpdates an existing monitor in the user's current team. Requires full API access (Pro/Business). The monitor type is fixed; only fields you pass are changed.
delete-monitor-toolPermanently deletes a monitor (and its history) in the user's current team. Requires full API access (Pro/Business). This cannot be undone.
pause-monitor-toolPauses a monitor (stops checks and alerts) in the user's current team. Requires full API access (Pro/Business).
unpause-monitor-toolResumes a paused monitor in the user's current team. Requires full API access (Pro/Business).
trigger-check-toolRuns an on-demand check of an existing monitor right now and returns the result. Requires full API access (Pro/Business).
create-incident-toolCreates a manual incident against a monitor in the user's current team. Requires full API access (Pro/Business).
update-incident-toolUpdates an incident's status and/or root cause in the user's current team. Requires full API access (Pro/Business). Marking it resolved sets the end time and duration.
delete-incident-toolPermanently deletes an incident in the user's current team. Requires full API access (Pro/Business). This cannot be undone.
resolve-incident-toolMarks an incident resolved in the user's current team, setting the end time and duration. Requires full API access (Pro/Business).
acknowledge-incident-toolAcknowledges an incident in the user's current team, logging an acknowledgment activity. Requires full API access (Pro/Business).