Security & Testing

domain-bannin.jp

Runs comprehensive health checks on public domains, covering email authentication, DNS infrastructure, and web security.

1 endpoint1 known toolsFirst detected August 17, 2026Last detected August 29, 2026

ENDPOINT 1

https://domain-bannin.jp/api/mcp

No auth detected

MCP server metadata

Name: domain-bannin
Version: 0.1.0

Capabilities

tools

Known tools 1

domain_diagnose

Runs a comprehensive health check on a public domain: SPF / DKIM / DMARC for the headline score, plus optional details on email-auth adjacent records (MX, BIMI, MTA-STS, TLS-RPT, DKIM key length), DNS infrastructure (NS, DNSSEC, CAA, AAAA, SOA, TXT), web security (HTTPS, certificate, HSTS, HTTP/2-3, CT log), domain registration (RDAP expiry, registrar lock, DS chain), and brand protection (typosquatting, TLD parity).

Potential side effects

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.domain-bannin]
url = "https://domain-bannin.jp/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "domain-bannin": {
      "type": "http",
      "url": "https://domain-bannin.jp/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: domain-bannin
Remote MCP URL: https://domain-bannin.jp/api/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": {
    "domain-bannin": {
      "url": "https://domain-bannin.jp/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "domain-bannin": {
      "type": "http",
      "url": "https://domain-bannin.jp/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "domain-bannin",
  "transport": "streamable-http",
  "url": "https://domain-bannin.jp/api/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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