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.

Robozukan (ロボ図鑑)

REMOTE · ROBOZUKAN.COM · SCANNED SEP 28

Japanese catalog of physical devices AI agents can control: connectivity ratings, APIs, sources.

Available components

71 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 Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 670 tokens (~167/item across 4 items; 4 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 Management3
  • Stability observed for 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 Robozukan (ロボ図鑑) MCP server?

Robozukan (ロボ図鑑) is a hosted endpoint at https://robozukan.com/api/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 · robozukan.com

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

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.

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

    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 28 Sept 2026 · Probed https://robozukan.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=robozukan.com CN=WE1,O=Google Trust Services,C=US 9 Aug 2026 7 Nov 2026 ECDSA 256 ECDSA-SHA256 3f76a56aca6aa9851366ba5fdc864064
SANs: robozukan.com, *.robozukan.com
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 robozukan.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
robozukan.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://robozukan.com/api/mcp Verified 200
http (plaintext) http://robozukan.com/api/mcp HTTPS enforced 308 https://robozukan.com/api/mcp
MCP tools · 4 exposed · ~400 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
get_device ~98

1台のデバイスについて、AI接続性と自律度の判定根拠、接続口(API/SDK/MCP/ハック)、必要なひと手間、出典と確認日、関連する接続ガイドを返す。slug は search_devices の結果から取る。

NameTypeReqDescription
slugstringyesデバイスの slug(例: switchbot-hub-2)

No output schema declared.

No examples provided.

get_rating_criteria ~53

AI接続性(AI-0〜AI-5)と自律度(1〜3)の判定基準を返す。数値の意味を説明するときに使う。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_guides ~70

機種別の接続ガイド・組み合わせレシピ・コラムの一覧(タイトル・概要・URL)を新しい順に返す。

NameTypeReqDescription
categorystring–guide=接続ガイド / recipe=レシピ / column=コラム

No output schema declared.

No examples provided.

search_devices ~179

ロボ図鑑の収録デバイスを検索する。語句(製品名・ブランド・概要の部分一致)、カテゴリ、AI接続性の下限、接続口の種類で絞り込める。条件を省くと全件をAI接続性の高い順に返す。

NameTypeReqDescription
categorystring–カテゴリ
interface_typestring–この種類の接続口を持つデバイスに限る
limitinteger–最大件数(1〜50)
min_ai_ratinginteger–AI接続性の下限(0〜5)
querystring–製品名・ブランド・概要に含まれる語句(例: SwitchBot, Tapo, ROS2)

No output schema declared.

No examples provided.

Common questions

What is the Robozukan (ロボ図鑑) MCP server?

Robozukan (ロボ図鑑) is an MCP server listed in the public MCP registry as com.robozukan/robozukan. Japanese catalog of physical devices AI agents can control: connectivity ratings, APIs, sources. This page covers its hosted endpoint (https://robozukan.com/api/mcp).

Is the Robozukan (ロボ図鑑) MCP server safe to use?

Robozukan (ロボ図鑑) scores 71 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 Robozukan (ロボ図鑑) MCP server expose?

Robozukan (ロボ図鑑) exposes 4 tools: search_devices, get_device, list_guides, get_rating_criteria. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

Does the Robozukan (ロボ図鑑) MCP server require authentication?

No. We connected to Robozukan (ロボ図鑑) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Robozukan (ロボ図鑑) MCP server still maintained?

Robozukan (ロボ図鑑) is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.