ellomind-booking
Registry code: 4b951bf0b2f92229
Check live availability and book therapy sessions with a Malayalam-speaking psychologist.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.ellomind.com/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 ellomind-booking live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is ellomind-booking free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ellomind-booking have?
- 4 tools: create_booking_draft, get_booking_status, check_availability, list_services.
- Is ellomind-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.9%· all time 98.9%
last good check
of 4 tools
- down → live
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- check therapist availability
- book a therapy session
- check a booking status
- list therapy session types and prices
- takes → gives
- data → data
- tools
- 3 reads1 changes 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
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_services reads open 8h ago
List session types and prices for booking therapy with ElloMind. Call before creating a booking so you use a valid session_type and plan_code.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linescreate_booking_draft changes data unknown never probed
Hold a specific slot and return a single-use pay link to hand the customer. Call check_availability first and use one of its times. Collect the customer's name, phone, and email first. The price is server-set; you cannot set an amount. Payment and consent stay with the customer.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "session_type", "plan_code", "slot_date", "slot_time", "name", "phone", "email" ], "properties": { "name": { "type": "string" }, "email": { "type": "string" }, "phone": { "type": "string", "description": "with country code, e.g. +91 98xxxxxxxx" }, "plan_code": { "enum": [ "single", "starter5", "preferred9", "committed11" ], "type": "string" }, "slot_date": { "type": "string", "description": "YYYY-MM-DD from check_availability" }, "slot_time": { "type": "string", "description": "HH:MM 24h IST from check_availability" }, "session_type": { "enum": [ "individual", "couples", "teen" ], "type": "string" } } }arguments 50 linesget_booking_status reads unknown never probed
Retrieve a booking's status and Meet link to show the customer in chat. The booking already confirms automatically on payment (the customer is emailed the invite + link) — this tool does NOT lock in or create anything, it only reads the current state. Call it when the customer asks. REQUIRES the poll_key from create_booking_draft; a ref on its own will not release the Meet link.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "ref", "poll_key" ], "properties": { "ref": { "type": "string", "description": "the booking ref, e.g. EM-XXXX" }, "poll_key": { "type": "string", "description": "the poll_key returned by create_booking_draft; required to retrieve the Meet link" } } }arguments 18 linescheck_availability reads unknown 8h ago
Real open time slots (IST) for a session type over a date range. Dates are YYYY-MM-DD.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "session_type", "from", "to" ], "properties": { "to": { "type": "string", "description": "end date YYYY-MM-DD" }, "from": { "type": "string", "description": "start date YYYY-MM-DD" }, "session_type": { "enum": [ "individual", "couples", "teen" ], "type": "string" } } }arguments 27 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 id4b951bf0b2f92229.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4b951bf0b2f92229/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4b951bf0b2f92229?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.