hebert-magic-booking
Registry code: 69907e77d4d75144
Book Rick Hebert — a Houston, Texas magician and mentalist (comedy close-up magic and mind reading for corporate events, weddings, and parties). Use list_packages and get_contact to answer questions, and book_event to submit a request on the user's behalf. Rick personally reviews and confirms every request — booking a date is never instant. Confirm the event details plus the user's name and an email or phone before calling book_event.
- endpoint
- https://hebertmagic.com/api/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 hebert-magic-booking live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is hebert-magic-booking free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does hebert-magic-booking have?
- 3 tools: book_event, list_packages, get_contact.
- Is hebert-magic-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.
90 days 98.6%· all time 98.6%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- request a booking for a magician
- list entertainment packages
- get performer contact details
- takes → gives
- text, data → data
- tools
- 2 reads1 sends messages
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
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_packages reads open 17h ago
List Rick Hebert's three booking formats (each custom-quoted): Strolling Close-Up, The Stand-Up Show, and The Full Evening. Use to help a user choose a format before booking.
{ "type": "object", "properties": {} }arguments 4 linesget_contact reads open 17h ago
Get Rick Hebert's contact details (phone, email) and the area he serves. Use when the user wants to reach Rick directly or asks where he performs.
{ "type": "object", "properties": {} }arguments 4 linesbook_event sends messages unknown never probed
Submit a request to book Rick Hebert for an event. This sends the details to Rick, who personally reviews every request and replies (usually within a day) to confirm availability, pricing, and details — it does NOT instantly confirm or hold a date. Collect the contact's name and at least an email or phone number before calling. Rick is based near Houston, TX and travels for the right event.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "Full name of the person booking." }, "email": { "type": "string", "description": "Contact email address. Provide this and/or a phone number." }, "phone": { "type": "string", "description": "Contact phone number. Provide this and/or an email." }, "format": { "type": "string", "description": "Preferred format, if known: 'Strolling Close-Up', 'The Stand-Up Show', or 'The Full Evening'. See list_packages. Omit if unsure — Rick will recommend." }, "message": { "type": "string", "description": "Anything else about the event or what they're looking for." }, "event_city": { "type": "string", "description": "City and/or venue. Rick is based near Houston, TX (Greater Houston: The Woodlands, Sugar Land, Galveston, Clear Lake) and travels for the right event." }, "event_date": { "type": "string", "description": "Event date in YYYY-MM-DD format. Omit or leave blank if not set yet." }, "event_time": { "type": "string", "description": "Approximate start time, e.g. '7:00 PM'." }, "event_type": { "type": "string", "description": "The occasion — e.g. wedding, corporate event, birthday party, holiday party, gala, fundraiser." }, "guest_count": { "type": "string", "description": "Approximate number of guests, e.g. '50' or '75-100'." }, "contact_pref": { "type": "string", "description": "How they'd prefer Rick to reach back — e.g. 'email', 'phone', or 'text'." } } }arguments 52 lines
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 id69907e77d4d75144.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/69907e77d4d75144/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/69907e77d4d75144?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.