SealGate
REMOTE · API.SEALGATE.JP · SCANNED SEP 25
既存のログインにパスキー (生体認証) を後付けする API (日本製)。登録・認証・失効・復旧を tool で組み込み、利用者のデータは開発者の手元に残る。API キーは管理画面で発行
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_credential). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1608 tokens (~100/item across 16 items; 15 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SealGate MCP server?
SealGate is a hosted endpoint at https://api.sealgate.jp/v1/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.
remote · api.sealgate.jp
claude mcp add --transport http jp-sealgate-sealgate 'https://api.sealgate.jp/v1/mcp'
{
"mcpServers": {
"jp-sealgate-sealgate": {
"url": "https://api.sealgate.jp/v1/mcp"
}
}
} {
"servers": {
"jp-sealgate-sealgate": {
"type": "http",
"url": "https://api.sealgate.jp/v1/mcp"
}
}
} [mcp_servers.jp-sealgate-sealgate] url = "https://api.sealgate.jp/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-sealgate-sealgate": {
"type": "remote",
"url": "https://api.sealgate.jp/v1/mcp",
"enabled": true
}
}
} openclaw mcp add jp-sealgate-sealgate --url 'https://api.sealgate.jp/v1/mcp' --transport streamable-http
mcp_servers:
jp-sealgate-sealgate:
url: "https://api.sealgate.jp/v1/mcp" {
"McpServers": {
"jp-sealgate-sealgate": {
"Transport": "http",
"Url": "https://api.sealgate.jp/v1/mcp"
}
}
} assistant mcp add jp-sealgate-sealgate -t streamable-http -u 'https://api.sealgate.jp/v1/mcp'
{
"mcpServers": {
"jp-sealgate-sealgate": {
"type": "http",
"url": "https://api.sealgate.jp/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “signup_url” rewrote its description, which is the text the model reads security
- Schema quality: 87 → 100 ▼ functional
- New tool “create_checkout” functional
- New tool “get_account” functional
- New tool “get_billing_portal” functional
- New tool “signup” functional
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://api.sealgate.jp/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.sealgate.jp | CN=YR2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 699ae7fd5919bc4fb54ab49f5af7969c5b3 |
| SANs: *.sealgate.jp, sealgate.jp | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sealgate.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| sealgate.jp. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sealgate.jp/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.sealgate.jp/v1/mcp | HTTPS enforced | 308 | https://api.sealgate.jp/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_checkout カード登録 (有料化) のリンクを作る ~137
従量課金 (その月の MAU で決まるステップ式、税抜) に切り替えるための Stripe Checkout の URL を返します。利用者にこの URL を開いてカードを入力してもらうと、その場で無料枠の上限が外れます (人の手はこの 1 回だけ)。メールアドレスの確認が済んだ組織だけが使えます。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
No output schema declared.
No examples provided.
get_account 組織と料金の状態 ~84
組織のプラン (free / metered / enterprise)、メールアドレスの確認が済んでいるか、今月の MAU と無料枠の上限を返します。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
No output schema declared.
No examples provided.
get_app アプリの設定 ~74
この API キーのアプリ (rp_id、許可オリジン、パスワード併存期限、Webhook URL) を返します。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
No output schema declared.
No examples provided.
get_billing_portal 請求の管理画面のリンク ~82
カードの変更・領収書・解約を行う Stripe の画面の URL を返します。カードを登録済みの組織だけが使えます。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
No output schema declared.
No examples provided.
get_integration_guide 組み込みガイド ~51
SealGate の組み込み方 (流れ、REST API、ブラウザ SDK、サーバー側の実装例、エラー、料金) を Markdown で返します。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stats 数字 ~75
MAU (6 か月)、登録完了数、直近 30 日のログイン成否、利用者数、鍵の種類を返します。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
No output schema declared.
No examples provided.
issue_recovery_token 復旧トークンを発行 ~119
端末をなくした利用者が別の端末でパスキーを登録し直すための 15 分有効のトークンを返します。本人確認は開発者側で済ませてから呼んでください。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| external_id | string | yes | – |
| reason | string | – | 監査ログに残す理由 |
No output schema declared.
No examples provided.
list_audit 監査ログ ~114
登録・ログイン・失効・復旧の記録を新しい順に返します。event と since で絞れます。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| event | string | – | login.failed など |
| limit | number | – | 件数 (既定 100、最大 1000) |
| since | string | – | ISO 8601 |
No output schema declared.
No examples provided.
list_credentials 利用者の鍵 ~89
利用者 (external_id) のパスキー一覧を返します。失効済みも含み、revoked_at で区別します。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| external_id | string | yes | 開発者側の利用者 ID |
No output schema declared.
No examples provided.
list_plans 料金 ~48
ステップ式の料金表 (税抜)。その月のログイン利用者数 (MAU) がどの帯に入るかで月額が決まります。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_users 利用者一覧 ~110
パスキーを登録した利用者 (external_id、表示名、有効な鍵の数、最終ログイン) を返します。q で external_id を部分一致で絞れます。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| limit | number | – | 件数 (既定 100) |
| q | string | – | external_id の部分一致 |
No output schema declared.
No examples provided.
revoke_credential 鍵を失効 ~76
パスキーを 1 本失効します。取り消せません。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| credential_id | string | yes | crd_ で始まる鍵の ID |
No output schema declared.
No examples provided.
revoke_user 利用者の鍵をすべて失効 ~80
利用者 (external_id) のパスキーをすべて失効します (退会・乗っ取り時)。取り消せません。 (api_key が必要: 管理画面で発行したキー)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API キー (sk_live_…) |
| external_id | string | yes | – |
No output schema declared.
No examples provided.
signup アカウントを作る ~256
メールアドレスと、パスキーを使うサイトのドメイン (rp_id) で SealGate の組織を作り、最初のアプリと API キーをその場で返します (パスワード不要)。無料枠 (月 1,000 MAU) ですぐ組み込みを始められます。利用者に確認リンク (verify_url) を開いてもらうとメールアドレスの確認が済み、カード登録 (create_checkout) ができるようになります。24 時間以内に開かれないと組織は停止します。
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | – | アプリ名 (省略すると rp_id) |
| string | yes | 利用者 (開発者) のメールアドレス | |
| origins | array | – | 許可するオリジン (例: https://example.jp)。省略すると https://<rp_id>。開発用に http://localhost:3000 も足せます |
| rp_id | string | yes | パスキーを使うサイトのドメイン (例: example.jp、login.example.jp) |
No output schema declared.
No examples provided.
signup_url 登録の案内 ~51
利用者本人がブラウザで登録するときの URL を返します (Google / GitHub / メールアドレス)。エージェントが登録するなら signup を使ってください。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the SealGate MCP server?
SealGate is an MCP server listed in the public MCP registry as jp.sealgate/sealgate. 既存のログインにパスキー (生体認証) を後付けする API (日本製)。登録・認証・失効・復旧を tool で組み込み、利用者のデータは開発者の手元に残る。API キーは管理画面で発行. This page covers its hosted endpoint (https://api.sealgate.jp/v1/mcp).
Is the SealGate MCP server safe to use?
SealGate scores 70 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 SealGate MCP server expose?
SealGate exposes 15 tools: get_integration_guide, list_plans, signup, signup_url, get_app, and 10 more. Their descriptions and schemas cost roughly 1,446 tokens of context every time the server is loaded.
Does the SealGate MCP server require authentication?
No. We connected to SealGate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SealGate MCP server still maintained?
SealGate is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.