BookingMaven
Registry code: f5b76a96ccd59cae
Book, reschedule and cancel appointments at any business on the BookingMaven marketplace.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.bookingmaven.com/mcp
- door code
- 350486f457b17d8d
- protocol
- JSONRPC ·0.2
- authentication
- none
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is BookingMaven live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is BookingMaven free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does BookingMaven have?
- 11 tools: Start Business Signup, Search Businesses, Book Appointment, Create Customer Account, Get Business Profile, Check Availability, Get Booking, Reschedule Appointment, ….
- Is BookingMaven 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.
90 days 98.3%· all time 97.4%
last good check
of 11 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- book an appointment at a local business
- reschedule an appointment
- cancel an appointment
- check appointment availability
- search service businesses by location
- takes → gives
- text → data
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes
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.
start-business-signup auth-required never probed
Get a link for a business owner to list their business on BookingMaven
search-businesses auth-required never probed
Find service businesses by location and optional category
book-appointment auth-required never probed
Reserve an appointment slot at a service business as a guest
create-account auth-required never probed
Get a signup link to create a BookingMaven account using a booking email
get-business auth-required never probed
Get full business details including services, staff, and hours
get-availability auth-required never probed
Get open appointment slots for a business on a specific date
get-booking auth-required never probed
Look up the status and time of an existing booking using its booking_id and lookup_token
reschedule-appointment auth-required never probed
Move an existing booking to a new time, checked for conflicts
cancel-appointment auth-required never probed
Cancel an existing booking using its booking_id and lookup_token
list-my-bookings auth-required never probed
List appointments booked with your email (requires a signed-in OAuth connection)
link-account auth-required never probed
Link guest bookings to a signed-in account (requires a signed-in OAuth connection)
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf5b76a96ccd59cae.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f5b76a96ccd59cae/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f5b76a96ccd59cae?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.