DomainCat

app.domaincatPublished by domaincat.appOfficial publisherv1.0.0Updated Nov 1, 2026

Monitor SSL certs (incl. origin behind Cloudflare), domain expiry, DNS, email auth and blacklists.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant monitor SSL certificates, domain expiry, DNS, email authentication and blacklists for domains.

What you can do
  • Check SSL certificate status, including the origin certificate behind Cloudflare
  • Track domain registration expiry dates
  • Inspect DNS records and configuration
  • Review email authentication settings
  • Check domain and IP blacklist listings
  • No individual tools are listed, so exact actions depend on the connected account and plan
When to use it
Useful when you want an assistant to keep an eye on domain health — expiring certificates or domains, DNS and email-auth misconfiguration, or blacklist problems — without leaving the chat to check each service separately.
Requirements
A remote MCP endpoint at domaincat.app over streamable HTTP; OAuth sign-in is required, so a DomainCat account is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a third-party service, which will see the domains you monitor. The manifest lists no tools, so confirm what the connection can read or change before authorizing.

Installation

In SourceWeft

  1. Open DomainCat 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/app.domaincat%2Fdomaincat/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": {
    "domaincat": {
      "type": "http",
      "url": "https://domaincat.app/api/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

1
  1. v1.0.0LatestNov 1, 2026

Score

83% 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
  • 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.