Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kata (型)

REMOTE · MCP.HAKUTO-0209.COM · SCANNED SEP 22

実在の日本のLP/HPを参考に返す。業種や雰囲気からURLと実測配色を数件。無料・鍵不要。

67 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 777 tokens (~777/item across 1 items; 1 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 Management20
  • Stability observed for 6 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the Kata (型) MCP server?

Kata (型) is a hosted endpoint at https://mcp.hakuto-0209.com/kata, 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

# add to Claude Code
claude mcp add --transport http com-hakuto-0209-kata 'https://mcp.hakuto-0209.com/kata'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-hakuto-0209-kata": {
      "url": "https://mcp.hakuto-0209.com/kata"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-hakuto-0209-kata": {
      "type": "http",
      "url": "https://mcp.hakuto-0209.com/kata"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-hakuto-0209-kata]
url = "https://mcp.hakuto-0209.com/kata"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hakuto-0209-kata": {
      "type": "remote",
      "url": "https://mcp.hakuto-0209.com/kata",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-hakuto-0209-kata --url 'https://mcp.hakuto-0209.com/kata' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-hakuto-0209-kata:
    url: "https://mcp.hakuto-0209.com/kata"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-hakuto-0209-kata": {
      "Transport": "http",
      "Url": "https://mcp.hakuto-0209.com/kata"
    }
  }
}
# add to Vellum
assistant mcp add com-hakuto-0209-kata -t streamable-http -u 'https://mcp.hakuto-0209.com/kata'
// mcp.json
{
  "mcpServers": {
    "com-hakuto-0209-kata": {
      "type": "http",
      "url": "https://mcp.hakuto-0209.com/kata"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 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.

  • 17 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 16 Sept 26 64

    First indexed and scored.

Diagnostics

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/kata

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 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

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/kata Verified 200
http (plaintext) http://mcp.hakuto-0209.com/kata HTTPS enforced 308 https://mcp.hakuto-0209.com/kata
MCP tools · 1 exposed · ~315 tokens

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 →

Tool Tokens
kata_reference ~315

HP・LP・UI を作る前に、実在の公開サイトを参考として引く。業種や雰囲気(例:「カフェのLP」「士業のコーポレート」「買取サービス」)を渡すと、日本で実際に公開されている LP/HP を数件、URL と実測した配色(+分かればフォント)で返す。生成AIが出しがちな『それっぽいだけ』のデザインを、実在サイトの型に寄せるために使う。さらに、その業種で使える無料画像(ボーの素材やさん)の直リンクを最大60点まとめて返す。画像が要る HP/LP/UI 制作では必ずこれを呼び、返ってきた画像を各セクションに置くこと(画像ゼロのセクションを作らない)。業種を省くと、収録している業種の一覧を返す。

NameTypeReqDescription
countinteger参考サイトの件数(既定5・最大10)。画像は業種に応じて別途最大60点返す
industry_or_vibestring業種か雰囲気(例: カフェのLP / 士業のコーポレート / 買取 / BtoB SaaS)。省略すると収録業種の一覧を返す

No output schema declared.

No examples provided.

Common questions

What is the Kata (型) MCP server?

Kata (型) is an MCP server listed in the public MCP registry as com.hakuto-0209/kata. 実在の日本のLP/HPを参考に返す。業種や雰囲気からURLと実測配色を数件。無料・鍵不要。 This page covers its hosted endpoint (https://mcp.hakuto-0209.com/kata).

Is the Kata (型) MCP server safe to use?

Kata (型) scores 67 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 Kata (型) MCP server expose?

Kata (型) exposes 1 tool: kata_reference. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.

Does the Kata (型) MCP server require authentication?

No. We connected to Kata (型) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kata (型) MCP server still maintained?

Kata (型) 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.