hakuto-0209-com-mcp.yml

HaneruTo operates ONE remote MCP server, b612, at https://mcp.hakuto-0209.com/mcp — the same host that serves its A2A agent card and JSON-RPC endpoint (Vercel origin b612-a2a.vercel.app). It is Streamable HTTP (a GET returns 406 application/json; POST with Accept: application/json, text/event-stream answers as text/event-stream), speaks MCP protocol version 2025-06-18, identifies itself as serverInfo {name: b612, version: 0.1.0}, and answers initialize, tools/list AND a tools/call on b612_principles anonymously. tools/list returns ten tools, every one with a real inputSchema (JSON Schema draft-07 where it has properties) and an execution.taskSupport of "forbidden" — the whole surface is synchronous reference lookups. resources/list and prompts/list return -32601 Method not found. The server's initialize instructions (Japanese) tell the connecting agent how to work: consult b612_patterns before starting a task, pull b612_domain_preset and b612_review_checklist, apply the findings locally, re-check before declaring done, and apply b612_rules to code locally — and state plainly that the server has no input for source code, so customer code never reaches the provider. The tool names, bilingual titles and the Japanese-law vocabulary (景表法/特商法/薬機法) match no shared platform fingerprint: this is a provider-built server. Third-party corroboration: listed on Glama as connector com.hakuto-0209/b612 (endpoint https://mcp.hakuto-0209.com/mcp, 10 tools, "Healthy", last tested 2026-09-20).

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.