Lets an assistant look up a domain's public configuration: SPF, DKIM, DMARC, DNS, SSL certificates, security headers, subdomains, and similar domains.
What you can do
This remote MCP server inspects the public configuration of a domain and returns findings to the assistant. According to its description, it covers SPF, DKIM and DMARC records, DNS, SSL certificates, security headers, subdomains, and look-alike domains. It works only from publicly available information, and the provider states no registration is required and it is free.
When to use it
Useful when you want an assistant to check a domain's email authentication and DNS records, review its TLS certificate or security headers, or survey subdomains and similar-looking domains. It suits quick reconnaissance and configuration review rather than anything that changes a domain.
Requirements
It is a remote streamable HTTP endpoint at domain-bannin.jp; nothing needs to be installed locally. The manifest declares no authentication, no environment variables, and no headers, so no account or API key appears to be needed. Network access to the endpoint is required.
Before you install
The server is operated by a third party, so the domain names you submit are sent to that provider. It reports on public information only and does not appear to write, send, or delete anything. Treat its findings as a starting point and verify important results against authoritative sources.
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/io.github.j-doi%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.
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
v0.1.0LatestSep 16, 2026
Score
75%
75% 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.
License10 pts
Declare a license in the repository or the registry entry.