mcp-registry/bot.meet/mcp · v1.3.0
As of 2026-10-26 20:36 UTC, the Meet MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
AI-native scheduling and booking: check availability, book meetings, share links.
Point your MCP client at this streamable-http endpoint: https://mcp.meet.bot
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fbot.meet%2Fmcp/fixes
{
"name": "book_meeting",
"description": "Book a new meeting slot",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"page",
"guest_email",
"guest_name",
"start"
],
"properties": {
"page": {
"type": "string",
"description": "The URL of the scheduling page (e.g. https://meet.bot/your-page)"
},
"notes": {
"type": "string",
"description": "Optional notes to include with the meeting (e.g. agenda, call details)"
},
"start": {
"type": "string",
"description": "Start time in ISO 8601 format (e.g. 2025-03-10T14:00:00Z); must be an available slot"
},
"guest_name": {
"type": "string",
"description": "Full name of the guest"
},
"guest_email": {
"type": "string",
"description": "Email address of the guest (used for calendar invite and confirmation)"
}
},
"additionalProperties": false
},
"annotations": {
"audience": [
"user",
"assistant"
],
"priority": 0.8,
"lastModified": "2025-03-05T00:00:00Z",
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Book Meeting"
}{
"name": "delete_webhook",
"description": "Delete one of the authenticated user's webhooks by id",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "number",
"description": "The webhook id to delete"
}
},
"additionalProperties": false
},
"annotations": {
"audience": [
"user",
"assistant"
],
"priority": 0.8,
"lastModified": "2025-03-05T00:00:00Z",
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Delete Webhook"
}{
"name": "get_available_slots",
"description": "Get available booking slots for a scheduling page",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"page"
],
"properties": {
"end": {
"type": "string",
"description": "End date for the range in YYYY-MM-DD format"
},
"page": {
"type": "string",
"description": "The URL of the scheduling page (e.g. https://meet.bot/your-page)"
},
"count": {
"type": "number",
"description": "Maximum number of slots to return (defaults to server limit)"
},
"start": {
"type": "string",
"description": "Start date for the range in YYYY-MM-DD format"
},
"timezone": {
"type": "string",
"description": "IANA timezone for slot times (e.g. America/New_York, Europe/London)"
},
"booking_link": {
"type": "boolean",
"description": "If true, include shareable booking links in the response"
}
},
"additionalProperties": false
},
"annotations": {
"audience": [
"user",
"assistant"
],
"priority": 0.8,
"lastModified": "2025-03-05T00:00:00Z",
"readOnlyHint": true
},
"title": "Get Available Slots"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/bot.meet/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/bot.meet/mcp"}) over MCP.
set_webhook ~325 tokensget_available_slots ~235 tokensbook_meeting ~217 tokensget_page_info ~96 tokensdelete_webhook ~85 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fbot.meet%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fbot.meet%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fbot.meet%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fbot.meet%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fbot.meet%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:975071b7e0ef4010…, first seen 2026-10-17, included at leaf 11084 of 75,326. Version history · verify what your client received.
Compare: most reliable calendar servers · most reliable communication servers · most reliable productivity servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 20:36 UTC, the Meet MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
Meet MCP server advertises 8 tools, including book_meeting, delete_webhook, get_available_slots, get_page_info, get_scheduling_pages.
Point your MCP client at this streamable-http endpoint: https://mcp.meet.bot
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.