tock-mcp

tock-mcp

MCP server for Tock (exploretock.com) — restaurant discovery and availability. Every request is relayed through the user's signed-in browser tab via the fetchproxy extension, so there's no cookie paste, no bot-wall dance, and no password handling.

• npm: npmjs.com/package/tock-mcp
• Source: github.com/chrischall/tock-mcp

Tock does not publish an official consumer API, and exploretock.com sits behind a Cloudflare challenge. This server fetches the same server-rendered pages the Tock web app uses (parsing their embedded window.$REDUX_STATE store) through your own signed-in browser tab. It is read-only: Tock reservations are prepaid tickets, so booking is left to exploretock.com. Use at your own discretion.

Setup

The MCP server is half of the picture — the other half is the fetchproxy browser extension that talks to Tock from your signed-in tab. Both are required.

1. Install the MCP server

Add to .mcp.json in your project or ~/.claude/mcp.json:

{
  "mcpServers": {
    "tock": {
      "command": "npx",
      "args": ["-y", "tock-mcp"]
    }
  }
}

Or from source:

git clone https://github.com/chrischall/tock-mcp
cd tock-mcp
npm install && npm run build
# then point .mcp.json at dist/bundle.js

2. Install the fetchproxy extension

tock-mcp shares a single browser extension with every other fetchproxy-based MCP. Install it once from github.com/chrischall/fetchproxy, then open exploretock.com and sign in (only needed for the account tools; discovery works signed-out).

3. Approve the one-time pair code

The first tool call prints a pair code to approve in the Transporter extension popup (trust-on-first-use, per identity). Run tock_healthcheck to trigger it, approve the code, and you're paired for good.

Tools

Typical flow

1. tock_list_metros { query: "chicago" } → find the metro slug.
2. tock_search_restaurants { metro: "chicago", query: "tasting menu" } → get venue slugs.
3. tock_get_availability { slug: "alinea", date: "2026-07-10", party_size: 2 } → see experiences and open dates/times.
4. To book, open exploretock.com/ — reservations are prepaid tickets and are completed on Tock.

Booking verification protocol

Booking happens outside these tools (on exploretock.com, by hand or by UI automation), but verification is this server's job. A booking counts as confirmed only when BOTH hold:

1. a confirmation ID, receipt URL, or confirmation email was captured, and
2. tock_verify_reservation { venue, date, partySize, bookedMinutesAgo } returns verdict confirmed.

Use tock_verify_reservation rather than reading tock_list_reservations yourself: it checks the canceled and past lists too (a created-then-voided booking appears only in canceled), and it applies the lag rule below for you, returning recheckAdvised: true when an absence is still inconclusive.

Anything less — including a screenshot of a success screen — must be reported as "attempted, unverified." Two Tock-specific traps make the stricter rule non-negotiable:

• The post-booking modal is not proof: a confirm submitted with a stale cart is a silent no-op that still renders the success modal.
• The reservations backend (PatronReservationHistory) lags the Reservations tab by minutes. A single immediate re-read proving absence proves nothing; re-query after a couple of minutes (and once more before giving a verdict).

Notes

• Read-only. No booking, cancelling, or payment — Tock reservations are prepaid/Turnstile-gated checkouts left to the site.
• Discovery needs no login. Only tock_list_reservations, tock_get_profile and tock_verify_reservation require a signed-in exploretock.com tab.
• Errors are actionable: a Cloudflare challenge asks you to clear it in the signed-in tab; a signed-out account tool asks you to sign in.