tock-mcp
Related Servers
Alternatives to tock-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, including managing booking history and handling multi-factor authentication.9132 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, with persistent sessions and MFA handling.9132 npm1MIT
- AlicenseBqualityFmaintenanceEnables users to search, check availability, and book restaurant reservations across Resy and OpenTable platforms. It supports direct booking for Resy and includes an automated reservation 'sniper' for securing high-demand slots the moment they become available.124MIT
- AlicenseAqualityCmaintenanceEnables Claude, Codex, Cursor, or any MCP client to find restaurants in Japan by location, walking time, party size, private room, cuisine, budget, and seating window, returning real availability for the requested date. It books them in two steps through the user's own signed-in Chrome, preparing a summary and confirmation token first and placing the reservation only after the user approves it.14MIT
- FlicenseNot gradedqualityDmaintenanceEnables restaurant reservation management through SevenRooms API, allowing users to create reservations and query available time slots with guest details and party size information.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents and clients to check table availability and book restaurant reservations for a given date, time, and party size, returning either a confirmed booking or the nearest alternative slots. It also supports idempotent retries so replayed requests return the original reservation rather than double-booking a table.-
TDQS
Scored across 8 tools
Each tool targets a distinct resource+action: metros, restaurant search, restaurant details, availability, reservations, profile, verification, and diagnostics. The only mild overlap is tock_get_restaurant vs tock_get_availability, since both surface bookable experiences and prices, but the descriptions clearly separate metadata from calendar/times.
All tools share the tock_ prefix and follow a verb_noun pattern (get_availability, list_reservations, search_restaurants, verify_reservation). The lone deviation is tock_healthcheck, which uses a noun rather than verb_noun, a minor break in an otherwise consistent scheme.
Eight tools is well-scoped for a read-only restaurant-discovery and reservation-lookup server. Each tool maps to a clear need (browse metros, search venues, inspect details/availability, review and verify reservations, diagnose the bridge) with no redundant entries.
The read-only surface covers discovery, availability, reservation listing, verification, and identity, so agent workflows avoid dead ends. Booking/cancellation are intentionally excluded and clearly documented, but there is no way to modify or cancel a reservation, leaving a minor gap for a bookings-oriented domain.