An agent can connect on its own if it already holds MEET_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://mcp.meet.botstreamable-http
api_key ${MEET_TOKEN}
yes
100%
416 ms
2025-06-18
2026-10-20
Tools (8)
book_meeting
Book a new meeting slot
delete_webhook
Delete one of the authenticated user's webhooks by id
get_available_slots
Get available booking slots for a scheduling page
get_page_info
Get information about a specific scheduling page
get_scheduling_pages
Get all scheduling pages for the authenticated user
health_check
Check if the Meet.bot API client is healthy and the Bearer token is valid
list_webhooks
List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)
set_webhook
Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS256) JSON payload to the URL on each booking event.