Remote MCP · Endpoint
ドメイン番人 MCP server
No. ドメイン番人 answered an MCP handshake 58 minutes ago.
UpLast checked 58 minutes ago
Server URL
https://domain-bannin.jp/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.j-doi/domain-bannin
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 441 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。
- Website
- https://domain-bannin.jp/
- Repository
- https://github.com/j-doi/domain-shield
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 58 minutes ago | Handshake completed | 441 ms |
| 1 day ago | Handshake completed | 427 ms |
| 2 days ago | Handshake completed | 1.06 s |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with ドメイン番人 and makes no claim about it beyond what these checks measured.