Remote MCP · Endpoint

ドメイン番人 MCP server

No. ドメイン番人 answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://domain-bannin.jp/api/mcp

The last check completed an MCP handshake.

Registry name
jp.domain-bannin/domain-bannin
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
266 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。
Listing
From the official MCP registry (active).
Recent checks of ドメイン番人
CheckedResultHandshake
9 hours agoHandshake completed266 ms
4 days agoHandshake completed566 ms
14 days agoHandshake completed515 ms
15 days agoHandshake completed1.11 s
15 days agoHandshake completed831 ms
17 days agoHandshake completed396 ms
18 days agoHandshake completed838 ms
19 days agoHandshake completed630 ms
20 days agoHandshake completed840 ms
21 days agoHandshake completed538 ms
23 days agoHandshake completed844 ms

The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.

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.