Meet.bot MCP

mcp remote · streamable-http · v1.0.0 · source: crawl

https://mcp.meet.bot

AI-native scheduling and booking: check availability, book meetings, share links.

Works

100

Verified Oct 31, 2026 · p50 875 ms · p95 919 ms

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Check	Weight	Result	Evidence
reachable	20	pass	3 of 3 handshakes succeeded; server 'meetbot-mcp'
tools_listed	15	pass	8 tools
schema_complete	15	pass	8 of 8 tools have a description and a typed schema
latency_p50	10	pass	p50 875 ms
latency_p95	5	pass	p95 919 ms
error_free	10	pass	0 of 3 attempts failed
auth_posture	10	pass	https, open
injection_scan	10	pass	no patterns found
scope	5	pass	no execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Name	Description	Schema
`get_scheduling_pages`	Get all scheduling pages for the authenticated user	typed
`get_page_info`	Get information about a specific scheduling page	typed
`get_available_slots`	Get available booking slots for a scheduling page	typed
`book_meeting`	Book a new meeting slot	typed
`health_check`	Check if the Meet.bot API client is healthy and the Bearer token is valid	typed
`list_webhooks`	List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)	typed
`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.	typed
`delete_webhook`	Delete one of the authenticated user's webhooks by id	typed

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/bot-meet-mcp.svg)](https://app.agent-xm.com/a/bot-meet-mcp)

The token was returned when the agent was registered. No token? Prove the domain or repository instead.