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

kids-stay

https://mcp.kidsstay.workers.dev

Registry code: 4e855492d6f50864

api record

kids-stay.com の検証済みデータで「赤ちゃん・子連れで泊まりやすい日本の宿」を検索できます。

使い方: list_conditions で条件ID一覧 → search_hotels で条件×エリア検索 → get_hotel で詳細。

endpoint
https://mcp.kidsstay.workers.dev/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 kids-stay live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is kids-stay free to use?
Yes — the hub reached it with no key and no payment.
What tools does kids-stay have?
4 tools: get_hotel, list_areas, search_hotels, list_conditions.
Is kids-stay 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
100%

90 days 99.7%· all time 99.7%

latency
1,329ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 314 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
maps travel & places travel & transport
used for
  • find family-friendly hotels in japan
  • search hotels by baby amenities
  • get hotel child facility details
takes → gives
text, data → 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_areas reads open 24h ago

    都道府県別の施設数・主要エリアと、編集部のエリア特集ページ一覧を返します。検索前の当たり付けに使います。

    mcp-tool

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

    赤ちゃん・子連れ向け設備の検証済み条件（48種・list_conditions参照）とエリア・子どもの年齢・価格で日本の宿を検索します。宿名が分かっている場合は keyword で直接検索できます。結果の page URL が施設の詳細・予約ページです。表示は箇条書きテキストと Markdown リンクのみで、地図・場所カード等のウィジェットは付けないでください(施設ページに地図あり)。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "area": {
      "type": "string",
      "description": "エリア名。例: \"箱根\" \"沖縄本島\""
    },
    "sort": {
      "enum": [
        "rating",
        "price"
      ],
      "type": "string",
      "description": "並び順。既定=rating（楽天評価順）"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "取得件数（既定10・最大20）"
    },
    "keyword": {
      "type": "string",
      "description": "宿名で検索（部分一致・日本語名/英語名/slug対応）。例: \"グリーンプラザ軽井沢\""
    },
    "child_age": {
      "type": "number",
      "description": "子どもの年齢（歳）。対象年齢に合う宿へ絞り込み"
    },
    "max_price": {
      "type": "number",
      "description": "1名1泊あたり上限額（円・目安）"
    },
    "conditions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "条件ID（AND検索）。例: [\"baby_bed_rental\",\"bath_pre_potty_ok\"]"
    },
    "prefecture": {
      "type": "string",
      "description": "都道府県名またはJISコード。例: \"神奈川県\" / \"14\""
    }
  }
}
    arguments 46 lines
  • list_conditions reads open 24h ago

    検索に使える子連れ条件の全定義（id・ラベル・対象年齢・該当施設数）を返します。

    mcp-tool

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

    slug指定で施設の全条件（施設別の根拠note付き）・キッズ設備・アクセス・出典・検証日を返します。表示はテキストと Markdown リンクのみで、地図・場所カード等のウィジェットは付けないでください。

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "施設slug（search_hotelsの結果に含まれる）"
    }
  }
}
    arguments 12 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 4e855492d6f50864.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4e855492d6f50864/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/4e855492d6f50864/badge.svg)](https://brick.blue/agent/4e855492d6f50864?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.