mcp-registry/io.github.j-doi/domain-bannin · v0.1.0
As of 2026-10-26 21:17 UTC, the J Doi Domain Bannin MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。
Point your MCP client at this streamable-http endpoint: https://domain-bannin.jp/api/mcp
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin/fixes
{
"name": "domain_diagnose",
"description": "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 ite",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Domain to diagnose, e.g. `example.co.jp`. A URL, an email address, a trailing dot, a port, or an internationalised name are all accepted and resolved to the registrable host — `https://日本語.jp/path`, `[email protected]` and `xn--wgv71a119e.jp` reach the same diagnosis. Names with no public suffix (`localhost`, an IP literal) are rejected."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Domain Health Diagnose"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.j-doi/domain-bannin"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.j-doi/domain-bannin"}) over MCP.
domain_diagnose ~277 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.j-doi%2Fdomain-bannin?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cc5c5aea846dc6b8…, first seen 2026-10-17, included at leaf 3045 of 75,499. Version history · verify what your client received.
Compare: most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 21:17 UTC, the J Doi Domain Bannin MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
J Doi Domain Bannin MCP server advertises 1 tool, including domain_diagnose.
Point your MCP client at this streamable-http endpoint: https://domain-bannin.jp/api/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.