b612 (hakuto AI)
REMOTE · MCP.HAKUTO-0209.COM · SCANNED SEP 22
Design-review copilot: industry design checkpoints, edge cases, and Japanese legal notes.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2553 tokens (~255/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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 b612 (hakuto AI) MCP server?
b612 (hakuto AI) is a hosted endpoint at https://mcp.hakuto-0209.com/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 · mcp.hakuto-0209.com
claude mcp add --transport http com-hakuto-0209-b612 'https://mcp.hakuto-0209.com/mcp'
{
"mcpServers": {
"com-hakuto-0209-b612": {
"url": "https://mcp.hakuto-0209.com/mcp"
}
}
} {
"servers": {
"com-hakuto-0209-b612": {
"type": "http",
"url": "https://mcp.hakuto-0209.com/mcp"
}
}
} [mcp_servers.com-hakuto-0209-b612] url = "https://mcp.hakuto-0209.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hakuto-0209-b612": {
"type": "remote",
"url": "https://mcp.hakuto-0209.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-hakuto-0209-b612 --url 'https://mcp.hakuto-0209.com/mcp' --transport streamable-http
mcp_servers:
com-hakuto-0209-b612:
url: "https://mcp.hakuto-0209.com/mcp" {
"McpServers": {
"com-hakuto-0209-b612": {
"Transport": "http",
"Url": "https://mcp.hakuto-0209.com/mcp"
}
}
} assistant mcp add com-hakuto-0209-b612 -t streamable-http -u 'https://mcp.hakuto-0209.com/mcp'
{
"mcpServers": {
"com-hakuto-0209-b612": {
"type": "http",
"url": "https://mcp.hakuto-0209.com/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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Schema quality: 2241 → 2553 ▼ functional
- New tool “b612_grow” functional
- 17 Sept 26 0
- Schema quality: 1954 → 2241 ▼ functional
- New tool “b612_reference” functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 76
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 22 Sept 2026 · Probed https://mcp.hakuto-0209.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.hakuto-0209.com | CN=YR1,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | RSA 2048 | SHA256-RSA | 678ba3e5166f813d1bccdd4df5643145236 |
| SANs: mcp.hakuto-0209.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 mcp.hakuto-0209.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hakuto-0209.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hakuto-0209.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.hakuto-0209.com/mcp | HTTPS enforced | 308 | https://mcp.hakuto-0209.com/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 →
b612_design HP/LP のデザイン規約を引く ~257
ホームページ・LP・UI・チラシを作る前に必ず引く。生成AIが出しがちで顧客に「AIくさい」と言われる形（注記の左に色の縦棒・器と同じ色の面・均一な3列カード・全部同じ角丸と影）の禁止事項と、カードは角張らせる・並びの間隔は親のgapで持つ・複雑なSVGは無料素材を使う、などの必須事項を返す。あわせて、放っておくと生成AIが出さない6つ（斜めの帯・斜めの文字・派手なCTA・追従CTA・写真の上の文字・飾りの浮遊）と、そのまま貼れるCSS/JSの一覧を返す。snippet に名前を渡すとその実装を全文返す。
| Name | Type | Req | Description |
|---|---|---|---|
| snippet | string | – | 実装が欲しいときにファイル名（例 cta-shine.css / sticky-cta.js）。省略すると規約と一覧を返す |
No output schema declared.
No examples provided.
b612_domain_preset b612 ドメインプリセット ~246
業種/ドメイン別の必須モデル・エッジケース・必須法令・アンチパターンを返す。対応ドメイン: accounting, ai-chat, ai-content-ops, android, beauty, blog, booking, chat, community, corporate, corporate-story, crm, ec, event, fukushi, game, healthcare, hr, instagram, inventory, ios, line, llmo, lms, lp, pos, project, rag, realestate, restaurant, retrogame, saas, seo, subscription, survey, task
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 業種/ドメイン名（例: ec, booking, healthcare, saas）。対応: accounting, ai-chat, ai-content-ops, android, beauty, blog, booking, chat, community, corporate, corporate-story, crm, ec, event, fukushi, game, healthc… |
No output schema declared.
No examples provided.
b612_grow SNS/note/AEOで売る型を引く（Grow層） ~312
作った HP/LP/商品/コンテンツを、SNS（X / Instagram / Threads）・note・AI検索（AEO）で広めて売るための戦略の作り方を返す。「集客したい」「SNS戦略」「売り方」「AEO」「AIの回答に出したい」「note を読まれたい」等で使う。7つの汎用原則＋チャネル別の型＋AEOの型に加え、生成AIが出しがちな戦略が抜かす『日本の法令ガード（ステマ規制・景表法・薬機法・特商法）』と『計測の実装（UTM・4指標）』を必ず含む。product に何を・誰に・いくらで売るか、goal に目標、channel に重点媒体を渡すと、その条件に当てて返す。
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | 重点チャネル（x / instagram / threads / note / aeo / all）。省略可 |
| goal | string | – | 目標（認知拡大 / リスト獲得 / 販売 など） |
| product | string | – | 何を・誰に・いくらで売るか（例: 980円の哲学エッセイ、決断できない人向け） |
No output schema declared.
No examples provided.
b612_notes 公式LINEに送ったメモを読む ~159
利用者が hakuto の公式LINE に送ったメモを読み込む。「今日のメモをまとめて」「昨日のメモ見せて」「今週のアイデア整理して」などと言われたらこれを使う。days で遡る日数を指定する（既定は1＝今日ぶん）。返ってくるのは日付ごとに並べた生のメモ。要約・分類・タスク化は、この結果を読んで自分で行うこと。
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 何日ぶん遡るか。今日だけなら 1、今週なら 7。既定は 1 |
No output schema declared.
No examples provided.
b612_patterns b612 実戦patterns ~195
b612 の実戦ノウハウ（典型エラー・推測実装の傾向・過去に効いた意思決定）を返す。案件固有名は含まない公開版。全文は約88,000字あるため、既定は見出し索引のみを返す。query に検索語を渡すと一致した節だけを返す（推奨）。
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | true で全文（max_chars の上限まで）。既定 false |
| max_chars | number | – | 出力の上限文字数（既定 20000）。超過分は落とした節名を明記する |
| query | string | – | 検索語（例: LINE, 決済, 予約, レスポンシブ）。未指定なら見出し索引 |
No output schema declared.
No examples provided.
b612_principles b612 の思考原則 ~72
b612 メソッドの思考の核（NO SPECULATION・実装前の3問自問・5原則・握りつぶし禁止）を返す。レビューや実装を始める前に読み、原則に沿って進めること。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
b612_reference 実在サイトの参考を引く（Honmono） ~287
HP・LP・UI を作る前に、実在の公開サイトを参考として引く。業種や雰囲気（例:「カフェのLP」「士業のコーポレート」「買取サービス」）を渡すと、日本で実際に公開されている LP/HP を数件、URL と実測した配色（＋分かればフォント）で返す。生成AIが出しがちな『それっぽいだけ』のデザインを、実在サイトの型に寄せるために使う。さらに、その業種で使える無料画像（ボーの素材やさん）の直リンクを最大60点まとめて返す。画像が要る HP/LP/UI 制作では必ずこれを呼び、返ってきた画像を各セクションに置くこと。業種を省くと、収録している業種の一覧を返す。
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | 返す件数（既定5・最大10） |
| industry_or_vibe | string | – | 業種か雰囲気（例: カフェのLP / 士業のコーポレート / 買取 / BtoB SaaS）。省略すると収録業種の一覧を返す |
No output schema declared.
No examples provided.
b612_review_checklist b612 レビュー観点（対象別） ~114
対象の種類に応じた b612 のレビュー観点を返す。返ってきた観点を使って呼び出し側の AI が実レビューを行う。対応: lp, hp, ec, api, saas, game, form, generic
| Name | Type | Req | Description |
|---|---|---|---|
| target_type | string | yes | レビュー対象の種類。次のいずれか: lp, hp, ec, api, saas, game, form, generic（不明なら generic） |
No output schema declared.
No examples provided.
b612_rules b612 検出ルール一覧 ~287
コードに当てる検出ルール（ID・重大度・なぜ危険か・直し方）の一覧を返す。**呼び出し側の AI がこのルールを手元のコードに当てて検査する**（コードは b612 サーバーに送らない）。握りつぶし / 秘密の直書き / 0行更新の見逃し / タイマー多重起動 / 印刷崩れ / 破壊的SQL / XSS 等。ルールID: swallow-empty-catch, swallow-catch-comment-only, swallow-nullish-default, swallow-nullish-any, supabase-update-without-select, hardcoded-secret, console-log-secret, raf-loop-not-idempotent, setinterval-no-clear, top-level-sdk-client, next-force-dynamic, print-transform-scale, global-element-selector, img-no-dimensions, destructive-sql, bulk-update-no-where, dangerous-html, eval-use, mcp-stdout-log, line-postback-encode, dark-body-light-surface, print-white-text, last-child-visual, aspect-ratio-with-object-position, tap-target-too-small, leftover-min-height, overflow-hidden-full-height, empty-element-no-fallback, fail-open-secret-check, charge-before-persist, fetch-result-ignored
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
b612_update b612 をアップデートする（資産を最新にする） ~156
b612 のアップデート。エージェント・法令ファイル・業種プリセット・雛形・参照ドキュメントを最新に更新する手順を返す。「b612 をアップデートして」「b612 を最新にして」と言われたらこれを使う。返ってきたコマンドを実行すると、手元と違うファイルだけが置き換わる（既存は .bak を残す）。新しい専門エージェントが増えたときや、法令が改正されたときに実行する。
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | 接続先（通常は指定不要） |
No output schema declared.
No examples provided.
What is the b612 (hakuto AI) MCP server?
b612 (hakuto AI) is an MCP server listed in the public MCP registry as com.hakuto-0209/b612. Design-review copilot: industry design checkpoints, edge cases, and Japanese legal notes. This page covers its hosted endpoint (https://mcp.hakuto-0209.com/mcp).
Is the b612 (hakuto AI) MCP server safe to use?
b612 (hakuto AI) scores 80 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 b612 (hakuto AI) MCP server expose?
b612 (hakuto AI) exposes 10 tools: b612_principles, b612_review_checklist, b612_patterns, b612_domain_preset, b612_rules, and 5 more. Their descriptions and schemas cost roughly 2,085 tokens of context every time the server is loaded.
Does the b612 (hakuto AI) MCP server require authentication?
Yes. b612 (hakuto AI) 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 b612 (hakuto AI) MCP server still maintained?
b612 (hakuto AI) is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.