SealGate
REMOTE · API.SEALGATE.JP
既存のログインにパスキーを追加する API (日本製)。プロジェクト・API キー・パスキー・監査ログを tool で扱う。管理画面のアカウントでログインしてつなぐ (OAuth)
Available components
Last scanned (20 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 28 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
- 27 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 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 0
- 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 0
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 21 Nov 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=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b6ead5813a967930132f9657c6f247e2 |
| SANs: sealgate.jp, api.sealgate.jp, *.api.sealgate.jp | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
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. | DS published | 6961 | 8 | Verified |
| sealgate.jp. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.sealgate.jp/.well-known/oauth-protected-resource/v1/mcp"
Bearer resource_metadata="https://api.sealgate.jp/.well-known/oauth-protected-resource/v1/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer resource_metadata="https://api.sealgate.jp/.well-known/oauth-protected-resource/v1/mcp" |
Protected resource metadata
| Document | https://api.sealgate.jp/.well-known/oauth-protected-resource/v1/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.sealgate.jp/v1/mcp |
| Authorisation server | https://app.sealgate.jp |
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 | Auth required | 401 | |
| http (plaintext) | http://api.sealgate.jp/v1/mcp | HTTPS enforced | 301 | 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.
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'
What is the SealGate MCP server?
SealGate is an MCP server listed in the public MCP registry as jp.sealgate/sealgate. 既存のログインにパスキーを追加する API (日本製)。プロジェクト・API キー・パスキー・監査ログを tool で扱う。管理画面のアカウントでログインしてつなぐ (OAuth). This page covers its hosted endpoint (https://api.sealgate.jp/v1/mcp).
Is the SealGate MCP server safe to use?
SealGate scores 38 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?
Yes. SealGate asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SealGate MCP server still maintained?
SealGate is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SealGate MCP server?
VerifyMCP ran 5 checks on SealGate, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about SealGate: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.