check_event_availability — WaitApp MCP Tool Read-only
check_event_availability
(check event availability) is one of 25 tools on the
WaitApp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_event_availability from your client
- Claude Code WaitApp check_event_availability run in your project directory
- Claude Desktop WaitApp check_event_availability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WaitApp check_event_availability ~/.cursor/mcp.json
- VS Code WaitApp check_event_availability .vscode/mcp.json
- Zed WaitApp check_event_availability ~/.config/zed/settings.json
- Windsurf WaitApp check_event_availability ~/.codeium/windsurf/mcp_config.json
- Cline WaitApp check_event_availability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WaitApp check_event_availability ~/.gemini/settings.json
- Grok WaitApp check_event_availability .mcp.json (in your project root)
- ChatGPT WaitApp check_event_availability Settings → Connectors → Advanced → Developer mode
- Claude.ai WaitApp check_event_availability Settings → Connectors → Add custom connector
- LangChain WaitApp check_event_availability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http waitapp https://waitapp.online/api/mcp
Other tools on this server
- search_venues
- list_room_types
- check_room_availability
- book_room
- list_events
- buy_ticket
- draft_delivery_order
- place_delivery_order
- confirm_delivery_order
- start_order_payment
- book_reservation
- check_service_availability
- book_service
- check_booking_status
- list_my_orders
- track_order
- cancel_order
- rate_order
- list_saved_locations
- save_location
- delete_saved_location
- get_connection_permissions
- view_photos
- list_menu_items
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.