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.
Что умеет
- 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
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
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
Список инструментов сервера (21)
Технические названия из tools/list. Нужны только разработчикам.
| 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 to answer "is anything down right now?". |
| 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 soon, response-time regressions, and open incidents. Use this to answer "what needs my attention?" or "anything I should know this morning?". |
| 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=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-tool | Gets details for a single monitor in the user's current team, including the latest response time per region and recent incidents. |
| list-incidents-tool | Lists 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-tool | Lists 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-tool | Lists 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-tool | Returns 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-tool | Returns 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-tool | Probe 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-tool | Creates 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-tool | Updates 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-tool | Permanently deletes a monitor (and its history) in the user's current team. Requires full API access (Pro/Business). This cannot be undone. |
| pause-monitor-tool | Pauses a monitor (stops checks and alerts) in the user's current team. Requires full API access (Pro/Business). |
| unpause-monitor-tool | Resumes a paused monitor in the user's current team. Requires full API access (Pro/Business). |
| trigger-check-tool | Runs an on-demand check of an existing monitor right now and returns the result. Requires full API access (Pro/Business). |
| create-incident-tool | Creates a manual incident against a monitor in the user's current team. Requires full API access (Pro/Business). |
| update-incident-tool | Updates 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-tool | Permanently deletes an incident in the user's current team. Requires full API access (Pro/Business). This cannot be undone. |
| resolve-incident-tool | Marks an incident resolved in the user's current team, setting the end time and duration. Requires full API access (Pro/Business). |
| acknowledge-incident-tool | Acknowledges an incident in the user's current team, logging an acknowledgment activity. Requires full API access (Pro/Business). |