_ registry / mcp http-sse · checked 49m ago

beaubi

https://beaubitw.com

Registry code: c00ee399515fdebc

api record

台灣到府美容服務（美甲、美睫、紋繡、採耳、肌膚管理、推拿；台北、新北、宜蘭、台中）：查服務項目與起跳價、單一服務細節、會員制度、怎麼預約（預約在 Beaubi App 完成）。

from a public catalogue that lists it, not from the operator

endpoint
https://beaubitw.com/api/mcp
protocol
http-sse ·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 beaubi live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is beaubi free to use?
Yes — the hub reached it with no key and no payment.
What tools does beaubi have?
5 tools: get_service, how_to_book, get_brand_info, list_services, get_membership.
Is beaubi 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
99.6%

90 days 99.6%· all time 99.6%

latency
437ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 462 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
lifestyle & home fashion & beauty
used for
  • list at-home beauty services and prices
  • get beauty service details
  • learn how to book a beauty appointment
  • get membership plan details
takes → gives
text → text
tools
5 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 5 tools
3 open 2 never probed 3 of 5 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.

  • get_brand_info reads open 24h ago

    Beaubi 行動美研是什麼、服務地區、怎麼預約、六大服務起跳價、會員制度、課程、常見問題。回答任何關於 Beaubi 的問題先呼叫這個。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • list_services reads open 24h ago

    六大到府服務（美甲、美睫、紋繡、採耳、肌膚管理、推拿）的項目、起跳價（TWD）、時長、加購。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_membership reads open 24h ago

    儲值方案、消費等級門檻與權益、會員限定組合。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_service reads unknown 16h ago

    指定服務類別的完整項目、價格、注意事項與常見問題。slug：nails、lashes、brows、ear-cleaning、skincare、massage。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "enum": [
        "nails",
        "lashes",
        "brows",
        "ear-cleaning",
        "skincare",
        "massage"
      ],
      "type": "string"
    }
  }
}
    arguments 20 lines
  • how_to_book reads unknown never probed

    回傳預約步驟與 App 連結。預約、選時段、付款都在 Beaubi App 內完成；本工具不能代為預約。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "service": {
      "type": "string",
      "description": "使用者想預約的服務名稱，僅用於說明"
    }
  }
}
    arguments 10 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 c00ee399515fdebc.

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

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.