Meet.bot MCP
REMOTE · MCP.MEET.BOT
AI-native scheduling and booking: check availability, book meetings, share links.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New prompt “book_for_guest” functional
- New prompt “check_availability” functional
- New prompt “list_my_pages” functional
- New prompt “schedule_meeting” functional
- New prompt “share_booking_link” functional
- New prompt “suggest_times” functional
- New tool “book_meeting” functional
- New tool “delete_webhook” functional
- New tool “get_available_slots” functional
- New tool “get_page_info” functional
- New tool “get_scheduling_pages” functional
- New tool “health_check” functional
- New tool “list_webhooks” functional
- New tool “set_webhook” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.meet.bot
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.meet.bot. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| bot. | present | 58741 | 8 | Verified |
| meet.bot. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.meet.bot | Unreachable | ||
| http (plaintext) | http://mcp.meet.bot | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_meeting Book Meeting ~133
Book a new meeting slot
| Name | Type | Req | Description |
|---|---|---|---|
| guest_email | string | yes | Email address of the guest (used for calendar invite and confirmation) |
| guest_name | string | yes | Full name of the guest |
| notes | string | – | Optional notes to include with the meeting (e.g. agenda, call details) |
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
| start | string | yes | Start time in ISO 8601 format (e.g. 2025-03-10T14:00:00Z); must be an available slot |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~32
Delete one of the authenticated user's webhooks by id
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The webhook id to delete |
No output schema declared.
No examples provided.
get_available_slots Get Available Slots ~138
Get available booking slots for a scheduling page
| Name | Type | Req | Description |
|---|---|---|---|
| booking_link | boolean | – | If true, include shareable booking links in the response |
| count | number | – | Maximum number of slots to return (defaults to server limit) |
| end | string | – | End date for the range in YYYY-MM-DD format |
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
| start | string | – | Start date for the range in YYYY-MM-DD format |
| timezone | string | – | IANA timezone for slot times (e.g. America/New_York, Europe/London) |
No output schema declared.
No examples provided.
get_page_info Get Page Information ~41
Get information about a specific scheduling page
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
No output schema declared.
No examples provided.
get_scheduling_pages Get Scheduling Pages ~19
Get all scheduling pages for the authenticated user
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health_check Health Check ~25
Check if the Meet.bot API client is healthy and the Bearer token is valid
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~32
List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_webhook Set Webhook ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | 'all' (default) fires for every page including ones created later; 'selected' only for the pages in `pages` |
| description | string | – | Optional label for the webhook |
| id | number | – | Webhook id to update; omit to create a new one |
| is_active | boolean | – | Whether the webhook is active (default true) |
| pages | array | – | Page ids to cover when coverage='selected' |
| scope | string | – | 'self' (default) your own pages; 'team' (team admins only) also fires for teammates' bookings |
| webhook_url | string | – | HTTPS URL we POST booking events to (required when creating) |
No output schema declared.
No examples provided.
How do I install the Meet.bot MCP server?
Meet.bot MCP is a hosted endpoint at https://mcp.meet.bot/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.meet.bot
claude mcp add --transport http bot-meet-mcp 'https://mcp.meet.bot/'
What is the Meet.bot MCP server?
Meet.bot MCP is listed in the public MCP registry as bot.meet/mcp. AI-native scheduling and booking: check availability, book meetings, share links. This page covers its hosted endpoint (https://mcp.meet.bot).
Is the Meet.bot MCP server safe to use?
Meet.bot MCP scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Meet.bot MCP server expose?
Meet.bot MCP exposes 8 tools: get_scheduling_pages, get_page_info, get_available_slots, book_meeting, health_check, and 3 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the Meet.bot MCP server require authentication?
Its publisher declares that Meet.bot MCP requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Meet.bot MCP server still maintained?
Meet.bot MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.