Domain Sentinel

com.domain-sentinelPublished by domain-sentinel.comOfficial publisherv1.2.0Updated Nov 5, 2026

Domain availability over RDAP, watchlists with daily or hourly checks, change history and alerts.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server for checking domain availability over RDAP, keeping watchlists with scheduled checks, and reviewing change history and alerts.

What you can do
  • Check whether domains are available using RDAP lookups
  • Create and manage watchlists of domains to monitor
  • Run scheduled checks on watched domains, daily or hourly
  • Review change history and receive alerts when a watched domain changes
When to use it
Useful when you want an assistant to research domain availability, track a set of candidate or competitor domains, and surface changes such as registration or status updates without checking each one by hand.
Requirements
A remote MCP endpoint at api.domain-sentinel.com using streamable HTTP; OAuth authentication is required. No environment variables or headers are declared, and no local package is needed.
Before you install
Access requires an OAuth sign-in to a third-party service, so the assistant acts on your account there. Watchlists and scheduled checks write data to that account, and alerts may depend on a paid plan, which the listing does not clarify.

Installation

In SourceWeft

  1. Open Domain 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/com.domain-sentinel%2Fdomain-sentinel/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": {
    "domain-sentinel": {
      "type": "http",
      "url": "https://api.domain-sentinel.com/mcp"
    }
  }
}

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

2
  1. v1.2.0LatestOct 6, 2026
  2. v1.0.0Sep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.