ドメイン番人

jp.domain-banninPublished by domain-bannin.jpOfficial publisherv0.2.0Updated Oct 30, 2026

ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant run a public health check on a domain: SPF, DKIM, DMARC, DNS, TLS certificates, security headers and related records.

What you can do
  • Diagnose a domain's email authentication: SPF, DKIM and DMARC, with an overall score and optional details on MX, BIMI, MTA-STS, TLS-RPT and DKIM key length
  • Inspect DNS infrastructure: NS, DNSSEC, CAA, AAAA, SOA and TXT records
  • Check web security: HTTPS, certificate, HSTS and HTTP/2-3
  • Look at subdomains and look-alike domains using public information only
When to use it
Useful when you want an assistant to audit a domain's email and DNS security posture, explain missing SPF/DKIM/DMARC records, or check certificate and header settings before or after a change.
Requirements
A remote streamable HTTP endpoint; no installation, account, API key or environment variables are declared. The assistant needs network access to the endpoint.
Before you install
Queries are made against public domain information, so the domains you ask about are sent to the third-party service. Results reflect only publicly visible records and may not match internal configuration.

Installation

In SourceWeft

  1. Open ドメイン番人 in the dashboard and add it to a workspace.
  2. 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/jp.domain-bannin%2Fdomain-bannin/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.

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

Tools

1

domain_diagnose

Domain Health 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). Returns a structured report with per-category scores, individual diagnostic items, and a `critical_issues` cross-cut summary. No authentication required.

Parametersdomainrequired

Version history

1
  1. v0.2.0LatestOct 30, 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 listedRequired15 pts
  • 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.

Other Domain-Bannin integrations