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

Belcome

https://belcome.app

Registry code: e0bbc4a381e16363

api record

Book appointments at salons, barbershops, spas, med spas and studios that use Belcome.

Flow: find_business, then list_services, then find_slots. Offer a few open times in the location's timezone and

endpoint
https://belcome.app/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 Belcome live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Belcome free to use?
Yes — the hub reached it with no key and no payment.
What tools does Belcome have?
3 tools: find_business, find_slots, list_services.
Is Belcome 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 100%· all time 100%

latency
313ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • find_business unknown 1h ago

    Find salons, barbershops, spas and studios that take online bookings on Belcome, by name, service or city. Returns up to 10 businesses with their locations and booking page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "near": {
          "type": "string",
          "description": "City, state or ZIP code to narrow the search, e.g. \"Orlando\" or \"02601\"."
        },
        "query": {
          "type": "string",
          "description": "Business name, service or kind of place, e.g. \"balayage\", \"barber\", \"Cape Cod Nails\"."
        }
      }
    }
    arguments 16 lines
  • find_slots unknown 1h ago

    Find open times for one service at a business, up to 14 days. Each time comes with a booking_url that opens the business's booking page with the service, professional and time already chosen; give that link to the person to confirm with their name and phone.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business",
        "service_id"
      ],
      "properties": {
        "from": {
          "type": "string",
          "description": "First day, YYYY-MM-DD in the location's timezone. Defaults to today."
        },
        "through": {
          "type": "string",
          "description": "Last day, YYYY-MM-DD, at most 13 days after from. Defaults to a week."
        },
        "business": {
          "type": "string",
          "description": "The business id returned by find_business."
        },
        "staff_id": {
          "type": "string",
          "description": "Only this professional. Leave out for anyone available."
        },
        "service_id": {
          "type": "string",
          "description": "Service id from list_services."
        },
        "location_id": {
          "type": "string",
          "description": "Location id. Defaults to the first location."
        }
      }
    }
    arguments 33 lines
  • list_services unknown 1h ago

    List the services a business offers online at one location: name, duration, price and the professionals who do each one. Use the ids with find_slots.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business"
      ],
      "properties": {
        "business": {
          "type": "string",
          "description": "The business id (\"business\" field) returned by find_business."
        },
        "location_id": {
          "type": "string",
          "description": "Location id from find_business. Defaults to the first location."
        }
      }
    }
    arguments 16 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 e0bbc4a381e16363.

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

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.