Remote MCP · Endpoint
SealGate MCP server
No. SealGate answered an MCP handshake 55 minutes ago.
UpLast checked 55 minutes ago
Server URL
https://api.sealgate.jp/v1/mcp
The last check completed an MCP handshake.
- Registry name
- jp.sealgate/sealgate
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.30 s
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 既存のログインにパスキー (生体認証) を後付けする API (日本製)。登録・認証・失効・復旧を tool で組み込み、利用者のデータは開発者の手元に残る。API キーは管理画面で発行
- Website
- https://sealgate.jp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 55 minutes ago | Handshake completed | 1.30 s |
| 1 day ago | Handshake completed | 608 ms |
| 2 days ago | Handshake completed | 922 ms |
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 SealGate and makes no claim about it beyond what these checks measured.