Meet.bot MCP
REMOTE · MCP.MEET.BOT · SCANNED SEP 20
AI-native scheduling and booking: check availability, book meetings, share links.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 619 tokens (~77/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_webhook" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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/'
{
"mcpServers": {
"bot-meet-mcp": {
"url": "https://mcp.meet.bot/"
}
}
} {
"servers": {
"bot-meet-mcp": {
"type": "http",
"url": "https://mcp.meet.bot/"
}
}
} [mcp_servers.bot-meet-mcp] url = "https://mcp.meet.bot/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bot-meet-mcp": {
"type": "remote",
"url": "https://mcp.meet.bot/",
"enabled": true
}
}
} openclaw mcp add bot-meet-mcp --url 'https://mcp.meet.bot/' --transport streamable-http
mcp_servers:
bot-meet-mcp:
url: "https://mcp.meet.bot/" {
"McpServers": {
"bot-meet-mcp": {
"Transport": "http",
"Url": "https://mcp.meet.bot/"
}
}
} assistant mcp add bot-meet-mcp -t streamable-http -u 'https://mcp.meet.bot/'
{
"mcpServers": {
"bot-meet-mcp": {
"type": "http",
"url": "https://mcp.meet.bot/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 −1
- 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 30 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
- 27 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 20 Sept 2026 · Probed https://mcp.meet.bot
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.meet.bot | CN=YE2,O=Let's Encrypt,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 697fde82b8a2191c7e181c449f42d804412 |
| SANs: mcp.meet.bot | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Verified | 200 | |
| http (plaintext) | http://mcp.meet.bot | HTTPS enforced | 301 | https://mcp.meet.bot/ |
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.
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?
No. We connected to Meet.bot MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Meet.bot MCP server still maintained?
Meet.bot MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.