# ドメイン番人 (remote · domain-bannin.jp)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `domain-bannin.jp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp.md), [page](https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp)

## Channel facts

- Endpoint: `https://domain-bannin.jp/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 246 tokens (~246/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the ドメイン番人 MCP server?

ドメイン番人 is a hosted endpoint at https://domain-bannin.jp/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http j-doi-domain-bannin 'https://domain-bannin.jp/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "j-doi-domain-bannin": {
      "url": "https://domain-bannin.jp/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.j-doi-domain-bannin]
url = "https://domain-bannin.jp/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "j-doi-domain-bannin": {
      "type": "remote",
      "url": "https://domain-bannin.jp/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add j-doi-domain-bannin --url 'https://domain-bannin.jp/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  j-doi-domain-bannin:
    url: "https://domain-bannin.jp/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "j-doi-domain-bannin": {
      "Transport": "http",
      "Url": "https://domain-bannin.jp/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add j-doi-domain-bannin -t streamable-http -u 'https://domain-bannin.jp/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `domain_diagnose` (~246 tokens)

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.

Input parameters:

- `domain` (string, required): 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`,…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 63
- 2026-09-06: 63
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59
- 2026-08-28: 58

## Common questions

### What is the ドメイン番人 MCP server?

ドメイン番人 is an MCP server listed in the public MCP registry as io.github.j-doi/domain-bannin. ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。 This page covers its hosted endpoint (https://domain-bannin.jp/api/mcp).

### Is the ドメイン番人 MCP server safe to use?

ドメイン番人 scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ドメイン番人 MCP server expose?

ドメイン番人 exposes 1 tool: domain_diagnose. Their descriptions and schemas cost roughly 246 tokens of context every time the server is loaded.

### Does the ドメイン番人 MCP server require authentication?

No. We connected to ドメイン番人 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ドメイン番人 MCP server still maintained?

ドメイン番人 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://domain-bannin.jp/api/mcp
- Repository: https://github.com/j-doi/domain-shield
- Website: https://domain-bannin.jp/
- Changelog RSS feed: https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/j-doi-domain-bannin/api-mcp