_ registry / mcp streamable-http · checked 2h ago

robozukan

https://robozukan.com

Registry code: ef09fddf67fd8da0

api record

ロボ図鑑(https://robozukan.com)は、AIエージェントから操作できる物理デバイス(スマートホーム・掃除ロボ・3Dプリンター・ドローン・カメラ・ロボットアーム・移動ロボ等)の日本語カタログです。

各デバイスにAI接続性(AI-0〜AI-5: 接続の口の有無と成熟度)と自律度(1〜3: 状態取得やフィードバックの段階)を付け、判定根拠と一次情報の出典(確認日つき)を持ちます。

endpoint
https://robozukan.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is robozukan live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is robozukan free to use?
Yes — the hub reached it with no key and no payment.
What tools does robozukan have?
4 tools: get_device, list_guides, search_devices, get_rating_criteria.
Is robozukan safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.5%

90 days 98.1%· all time 98.1%

latency
2,302ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 538 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search devices controllable by ai agents
  • get a device's ai connectivity rating
  • list device connection guides
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_guides reads open 7h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "category": {
          "enum": [
            "guide",
            "recipe",
            "column"
          ],
          "type": "string",
          "description": "guide=接続ガイド / recipe=レシピ / column=コラム"
        }
      }
    }
    arguments 15 lines
  • search_devices reads open 24h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "最大件数(1〜50)"
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "製品名・ブランド・概要に含まれる語句(例: SwitchBot, Tapo, ROS2)"
        },
        "category": {
          "enum": [
            "smart-home",
            "vacuum",
            "3d-printer",
            "drone",
            "camera",
            "robot-arm",
            "mobile-robot",
            "agriculture",
            "security",
            "other"
          ],
          "type": "string",
          "description": "カテゴリ"
        },
        "min_ai_rating": {
          "type": "integer",
          "maximum": 5,
          "minimum": 0,
          "description": "AI接続性の下限(0〜5)"
        },
        "interface_type": {
          "enum": [
            "cloud-api",
            "local-api",
            "sdk",
            "mcp-official",
            "mcp-community",
            "hack"
          ],
          "type": "string",
          "description": "この種類の接続口を持つデバイスに限る"
        }
      }
    }
    arguments 53 lines
  • get_rating_criteria reads open 24h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_device reads unknown 24h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9-]{1,80}$",
          "description": "デバイスの slug(例: switchbot-hub-2)"
        }
      }
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ef09fddf67fd8da0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ef09fddf67fd8da0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ef09fddf67fd8da0/badge.svg)](https://brick.blue/agent/ef09fddf67fd8da0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.