Sentinel

io.rootstuffPublished by rootstuff.ioOfficial publisherv1.1.0Updated Oct 24, 2026

Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Hosted Sentinel MCP server that lets an assistant query and manage uptime, SSL, DNS and domain-expiry monitoring for client websites.

What you can do
  • Read uptime summaries, attention digests, monitors, incidents, performance and DNS history, expiring certificates, status pages, groups and team access
  • Run an on-demand URL check from every region
  • Create, update, pause, unpause and delete monitors, and trigger a re-check
  • Create, update, delete, acknowledge and resolve incidents
  • Create, update and delete monitor groups
When to use it
Useful for agencies and freelancers who already run Sentinel monitoring and want to ask about downtime, expiring certificates or team access, or set up and adjust monitors for client sites, from a chat client instead of the dashboard.
Requirements
Remote Streamable HTTP endpoint; nothing to install. Authentication is OAuth 2.1 (browser sign-in, dynamic client registration) or an Authorization bearer API token created in the Sentinel account. A Sentinel account and team are required; the on-demand URL check needs a paid plan.
Before you install
The bearer token grants access to the account's monitoring data and, with the right permissions, to write tools. Write tools need a verified email and share an hourly change budget; deletes are irreversible. All access is scoped to the authenticated user's current team, and the service is closed source and hosted by a third party.

Installation

In SourceWeft

  1. Open Sentinel in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.rootstuff%2Fsentinel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sentinel": {
      "type": "http",
      "url": "https://sentinel.rootstuff.io/mcp/sentinel-oauth"
    }
  }
}

README

[Sentinel logo]

Sentinel Monitoring MCP Server

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

Sentinel is uptime, SSL, DNS and domain-expiry monitoring built for agencies and freelancers managing client websites. This MCP server puts the whole product in your AI assistant: 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 creating, updating, pausing and deleting monitors, on-demand URL checks from every region, uptime summaries, incident management, DNS history, performance history, expiring-certificate reports, status pages, monitor groups, a team-members access review (roles, 2FA, last sign-in), and a needs-attention digest. Built by a solo founder who uses it daily instead of the dashboard.

[Sentinel dashboard: monitor stats and global check network]

This is a hosted (remote) MCP server; there is nothing to install or run. This repository is its public home: connection instructions, the registry manifest, and the issue tracker for feedback from agent users.

  • Endpoint (API token / bearer): https://sentinel.rootstuff.io/mcp/sentinel
  • Endpoint (OAuth 2.1): https://sentinel.rootstuff.io/mcp/sentinel-oauth
  • Transport: Streamable HTTP
  • Docs: sentinel.rootstuff.io/docs/mcp · Tool reference

Connect

Claude Code

bash
claude mcp add --transport http sentinel https://sentinel.rootstuff.io/mcp/sentinel \  --header "Authorization: Bearer YOUR_API_TOKEN"

Create an API token at sentinel.rootstuff.io/user/api-tokens.

Claude Desktop

Add a custom connector (Settings → Connectors → Add custom connector) with the URL https://sentinel.rootstuff.io/mcp/sentinel-oauth, or use the bearer endpoint above in a JSON config:

json
{  "mcpServers": {    "sentinel": {      "type": "http",      "url": "https://sentinel.rootstuff.io/mcp/sentinel",      "headers": {        "Authorization": "Bearer YOUR_API_TOKEN"      }    }  }}

Claude.ai (web and mobile apps)

Add a custom connector with the URL https://sentinel.rootstuff.io/mcp/sentinel-oauth. The Claude.ai connector flow requires OAuth; you'll sign in to Sentinel and approve access, no token pasting needed. Supports OAuth 2.1 with dynamic client registration.

ChatGPT and other MCP clients

Any client that speaks MCP over Streamable HTTP works. Use the OAuth endpoint for clients with a browser sign-in flow, or the bearer endpoint with an Authorization: Bearer YOUR_API_TOKEN header for headless and CLI clients.

Tools (26)

Monitoring reads (any plan with API access):

ToolWhat it answers
get-uptime-summary-tool"Is anything down right now?"
get-attention-items-tool"What needs my attention this morning?"
list-monitors-tool / get-monitor-toolInspect monitors, filter and search
list-incidents-toolReview outages and their timelines
get-performance-history-toolResponse-time trends per monitor
get-dns-history-toolDNS record changes over time
list-expiring-certificates-tool"Which SSL certificates expire soon?"
list-status-pages-toolPublic status pages in the team
list-groups-toolMonitor groups (the dashboard's grouped view)
list-team-members-toolWho has access: role, 2FA state, last sign-in
check-url-toolOn-demand check of any URL from every region

Monitor and incident management (write tools; a token with the matching permission):

ToolWhat it does
create-monitor-tool / update-monitor-tool / delete-monitor-toolManage monitors
pause-monitor-tool / unpause-monitor-toolPause checks during maintenance
trigger-check-toolRe-check a monitor right now
create-incident-tool / update-incident-tool / delete-incident-toolManage incidents
acknowledge-incident-tool / resolve-incident-toolWork an incident from chat
create-group-tool / update-group-tool / delete-group-toolOrganize monitors into groups

Example prompts

  • "Which of my client sites had downtime this week?"
  • "List SSL certificates expiring in the next 30 days."
  • "Create a monitor for https://client-site.com and check it now."
  • "Anything that needs my attention this morning?"
  • "Check if example.com is up from every region."
  • "Does everyone on my team have two-factor auth enabled?"

Authentication and plans

  • API tokens carry per-token permissions; write tools require the matching create, update, or delete permission on the token, and a refusal names the missing permission.
  • Plans: every tool is available on every plan, including Free (no card required), within the plan's monitor limit. Write tools (create, update, delete, pause) need a verified email on the account and share a per-team hourly budget of changes (30 on Free, 300 on paid plans). The on-demand check-url-tool needs a paid plan. See pricing.
  • All access is scoped to the authenticated user's current team. Deletes are irreversible.

About

Sentinel is a hosted service by rootstuff; the server code is not open source. This repository exists so MCP directories, registries, and agent users have a public home for the server. Bug reports and tool requests are welcome in the issues.

Source: README.md at commit f0c07d2

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.