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

craftme-booking

https://www.craftme.app

Registry code: 9cf7124497f5ccf6

api record

CraftMe lists craftsperson studios with online booking (all trades: electrical, plumbing, heating, roofing, painting, tiling, flooring, carpentry, windows, garden, cleaning and moving). Flow: search_studios → get_studio → find_free_slots → prepare_booking. prepare_booking never books: always give the user the confirm_url so they confirm themselves. Times are in the studio time zone.

endpoint
https://www.craftme.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 craftme-booking live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is craftme-booking free to use?
Yes — the hub reached it with no key and no payment.
What tools does craftme-booking have?
4 tools: search_studios, get_studio, prepare_booking, find_free_slots.
Is craftme-booking 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
58ms

last good check

priced tools
0

of 4 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 4 tools
4 never probed 0 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.

  • search_studios unknown 1h ago

    Find bookable craftsperson studios on CraftMe near a location or in a city, nearest first. Optionally only studios with a matching service.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, used when no coordinates are known"
    },
    "limit": {
      "type": "integer",
      "description": "Max studios, default 10, at most 20"
    },
    "latitude": {
      "type": "number"
    },
    "longitude": {
      "type": "number"
    },
    "radius_km": {
      "type": "number",
      "description": "Search radius around the coordinates, default 25"
    },
    "service_query": {
      "type": "string",
      "description": "Words the service name must contain, e.g. \"electrician\""
    }
  }
}
    arguments 27 lines
  • get_studio unknown 1h ago

    Name, address, rating and the bookable services (id, duration, price) of one studio.

    mcp-tool

    {
  "type": "object",
  "required": [
    "studio_id"
  ],
  "properties": {
    "studio_id": {
      "type": "string",
      "description": "studio_id from search_studios (or the handle from a profile link)"
    }
  }
}
    arguments 12 lines
  • prepare_booking unknown never probed

    Checks that the time is still free and returns a confirm_url. Nothing is booked yet: the user opens the link, signs in and confirms (deposit and terms of the studio apply there).

    mcp-tool

    {
  "type": "object",
  "required": [
    "studio_id",
    "service_id",
    "date",
    "start_time"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "studio_id": {
      "type": "string",
      "description": "studio_id from search_studios (or the handle from a profile link)"
    },
    "service_id": {
      "type": "string"
    },
    "start_time": {
      "type": "string",
      "description": "HH:mm in the studio time zone"
    },
    "employee_id": {
      "type": "string",
      "description": "Optional, group studios"
    }
  }
}
    arguments 30 lines
  • find_free_slots unknown 1h ago

    Free start times for one service, in the studio's time zone. Days from tomorrow up to 90 days ahead, at most 14 days per call. A time with a promotion field has a discount of the studio (percent, discounted price); it applies automatically when booked.

    mcp-tool

    {
  "type": "object",
  "required": [
    "studio_id",
    "service_id"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "description": "Number of days, default 7, at most 14"
    },
    "from_date": {
      "type": "string",
      "description": "YYYY-MM-DD, default tomorrow"
    },
    "studio_id": {
      "type": "string",
      "description": "studio_id from search_studios (or the handle from a profile link)"
    },
    "service_id": {
      "type": "string"
    },
    "employee_id": {
      "type": "string",
      "description": "Only this employee (group studios)"
    },
    "latest_time": {
      "type": "string",
      "description": "HH:mm, only times starting at or before"
    },
    "earliest_time": {
      "type": "string",
      "description": "HH:mm, only times starting at or after"
    }
  }
}
    arguments 36 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 9cf7124497f5ccf6.

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