Skip to main content
Glama
chrischall

tock-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tock-mcp

No user-submitted related servers found.

    Related Servers

    • SevenRooms MCP Server

      csnkarthik
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables restaurant reservation management through SevenRooms API, allowing users to create reservations and query available time slots with guest details and party size information.
      -

    • Restaurant Reservations MCP

      oluwatosinolamilekan
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -

    • FLUX Restaurants MCP Server

      sabamen88
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An AI-native restaurant discovery service that enables searching and receiving natural language recommendations for over 2,200 restaurants across 15+ US cities. It provides tools for accessing detailed restaurant info, curated lists, and cuisine-specific searches through the Model Context Protocol.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Every tool targets a distinct resource/action: reservation listing vs. availability vs. metro listing vs. profile vs. verification vs. venue detail vs. search vs. bridge diagnostics. There is no meaningful overlap; even the closely related get_restaurant/search_restaurants and list_reservations/verify_reservation have clearly separated roles.

    Naming Consistency4/5

    Almost all tools follow a clean tock_verb_noun pattern (list_reservations, get_availability, list_metros, get_profile, verify_reservation, get_restaurant, search_restaurants) with a consistent tock_ prefix. Only healthcheck breaks the verb_noun convention, a minor deviation.

    Tool Count5/5

    Eight tools is well-scoped for a restaurant discovery/verification server, and each one earns its place (discovery, availability, reservations, profile, verification, diagnostics). Nothing feels redundant or padded.

    Completeness3/5

    The read surface is solid for discovery and checking reservations, but the server is explicitly read-only: it cannot book or cancel a reservation, even though verify_reservation acknowledges booking attempts and canceled reservations exist. Menus/reviews are also absent, leaving notable gaps in the reservation lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources