Is the Hakuto 0209 B612 MCP server down?

mcp-registry/com.hakuto-0209/b612 · v0.1.0

healthy
Last checked 2026-10-20 17:36 UTC · handshake 125ms

As of 2026-10-20 17:36 UTC, the Hakuto 0209 B612 MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,987
outages (90d)
0
tools
10

Design-review copilot: industry design checkpoints, edge cases, and Japanese legal notes.

Install Hakuto 0209 B612 MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http hakuto-0209-b612-mcp-server https://mcp.hakuto-0209.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "hakuto-0209-b612-mcp-server": {
      "type": "http",
      "url": "https://mcp.hakuto-0209.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 3 warning(s) across 10 tool(s); ~1,432 tokens of tool definitions.
Scores higher than 36% of 15,413 MCP servers Glimind has audited.
Its tool list costs an agent ~1,432 tokens per session — lighter than 60% of servers.
81 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints12
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: b612_design, b612_domain_preset, b612_grow, b612_notes, b612_patterns and 5 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: b612_update

Handshake + tools/list takes ~1,855 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.hakuto-0209%2Fb612/fixes

b612_review_checklist 1 change 
{
  "name": "b612_review_checklist",
  "description": "対象の種類に応じた b612 のレビュー観点を返す。返ってきた観点を使って呼び出し側の AI が実レビューを行う。対応: lp, hp, ec, api, saas, game, form, generic",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "target_type"
    ],
    "properties": {
      "target_type": {
        "type": "string",
        "description": "レビュー対象の種類。次のいずれか: lp, hp, ec, api, saas, game, form, generic（不明なら generic）"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "b612 レビュー観点（対象別）"
}
b612_update 1 change 
{
  "name": "b612_update",
  "description": "b612 のアップデート。エージェント・法令ファイル・業種プリセット・雛形・参照ドキュメントを最新に更新する手順を返す。「b612 をアップデートして」「b612 を最新にして」と言われたらこれを使う。返すのは利用者本人が自分で実行する更新手順で、実行すると手元と違うファイルだけが置き換わる（既存は .bak を残す）。新しい専門エージェントが増えたときや、法令が改正されたときに実行する。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "base_url": {
        "type": "string",
        "description": "接続先（通常は指定不要）"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  },
  "title": "b612 をアップデートする（資産を最新にする）"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.hakuto-0209/b612"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.hakuto-0209/b612"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hakuto-0209%2Fb612.svg)](https://glimind.com/server/mcp-registry%2Fcom.hakuto-0209%2Fb612?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.hakuto-0209%2Fb612?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hakuto-0209%2Fb612.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hakuto-0209%2Fb612.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.hakuto-0209%2Fb612?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:252a8c27641708f6…, first seen 2026-10-17, included at leaf 943 of 34,175. Version history · verify what your client received.

Tools (10)

Compare: most reliable knowledge servers · most reliable code servers · most reliable devops servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hakuto 0209 B612 MCP server down right now?

As of 2026-10-20 17:36 UTC, the Hakuto 0209 B612 MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Hakuto 0209 B612 MCP server provide?

Hakuto 0209 B612 MCP server advertises 10 tools, including b612_design, b612_domain_preset, b612_grow, b612_notes, b612_patterns.

How do I install Hakuto 0209 B612 MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.hakuto-0209.com/mcp

Is the Hakuto 0209 B612 MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hakuto 0209 B612 MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve