Security & Testing

otterwatch.dev

Checks SSL/TLS certificates for domains, returning details like issuer, validity, and expiration.

1 endpoint2 known toolsFirst detected June 24, 2026Last detected July 29, 2026

ENDPOINT 1

https://otterwatch.dev/mcp

No auth detected

MCP server metadata

Name: Otterwatch SSL Certificate Check
Version: 1.0.0

Capabilities

loggingtools.listChanged

Known tools 2

check_domains_batch

Check the SSL/TLS certificates for several domains at once (up to 20) and return one result object per domain.

Inferred read-only

check_ssl_cert

Check the live SSL/TLS certificate for a domain and return its issuer, subject, validity dates, days remaining until expiry, chain validity, subject alternative names, and negotiated TLS version.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.otterwatch-ssl-certificate-check]
url = "https://otterwatch.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "otterwatch-ssl-certificate-check": {
      "type": "http",
      "url": "https://otterwatch.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: otterwatch-ssl-certificate-check
Remote MCP URL: https://otterwatch.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "otterwatch-ssl-certificate-check": {
      "url": "https://otterwatch.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "otterwatch-ssl-certificate-check": {
      "type": "http",
      "url": "https://otterwatch.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "otterwatch-ssl-certificate-check",
  "transport": "streamable-http",
  "url": "https://otterwatch.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for otterwatch.dev was fetched 2026-09-18T13:28:19.687Z.

Trust status Neutral

otterwatch.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.