SealGate
既存のログインにパスキーを追加する API (日本製)。プロジェクト・API キー・パスキー・監査ログを tool で扱う。管理画面のアカウントでログインしてつなぐ (OAuth)
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://api.sealgate.jp/v1/mcp | registry |
|---|---|---|
| Website | sealgate.jp | registry |
| Handshake | Answers, but requires sign-in before the handshake (824 ms) | our check, 2026-11-18 |
| Registry version | 1.4.1 · active · updated 2026-10-20 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http sealgate https://api.sealgate.jp/v1/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- gateway MCP gateway with runtime security policy, tool-call-level control, and audit of agent…
- Sealgate Sealgate gateway proxy: list governed MCP servers and review agent session and audit…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/jp.sealgate/sealgate)<a href="https://openforallofus.com/tools/jp.sealgate/sealgate"><img src="https://openforallofus.com/badge/jp.sealgate/sealgate.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name jp.sealgate/sealgate.