Skip to main content
Glama
chrischall

tock-mcp

by chrischall
README.md
# tock-mcp

MCP server for **Tock** ([exploretock.com](https://www.exploretock.com)) — restaurant discovery and availability for Claude. List cities, search a metro, and get a venue's details plus its bookable experiences, prices, party sizes, and open dates/times.

Every request is relayed through your own signed-in browser tab via the [ContextMint Bridge](https://github.com/nullnet-app/contextmint-bridge/releases) browser extension — no cookie paste, no bot-wall dance, no password handling. This project was developed and is maintained by AI (Claude Code).

> Tock publishes no official consumer API, and exploretock.com sits behind a Cloudflare challenge. tock-mcp fetches the same server-rendered pages the Tock web app uses (parsing their embedded `window.$REDUX_STATE` store) through your signed-in tab. It is **read-only** — Tock reservations are prepaid tickets, so booking stays on exploretock.com. Use at your own discretion.

## Install

```json
// .mcp.json
{
  "mcpServers": {
    "tock": { "command": "npx", "args": ["-y", "tock-mcp"] }
  }
}
```

You also need **ContextMint Bridge** (the browser extension shared by every fetchproxy-based MCP), installed from [its releases page](https://github.com/nullnet-app/contextmint-bridge/releases): in Chrome, unzip the chrome zip and load it unpacked (`chrome://extensions` → Developer mode → Load unpacked). Safari isn't available yet (it will ship inside the ContextMint app, which has no public download), so use Chrome for now. ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (https://github.com/chrischall/fetchproxy#extension) points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the `.sha256` file published beside it (`shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256`). Keep an exploretock.com tab open. The first tool call prints a one-time pair code to approve in the ContextMint Bridge popup — run `tock_healthcheck` to trigger it. Discovery works signed-out; the account tools need you signed in to exploretock.com.

## Tools

- **`tock_list_metros`** — Tock cities/metros with business counts; filter by name/country.
- **`tock_search_restaurants`** — venues in a metro slug (cuisine, price, neighborhood, slug).
- **`tock_get_restaurant`** — venue details + its bookable experiences.
- **`tock_get_availability`** — a venue's bookable calendar (experiences, prices, open dates/times).
- **`tock_list_reservations`** / **`tock_get_profile`** — the signed-in user's purchases and profile.
- **`tock_verify_reservation`** — after a booking attempt, re-query the account and return an explicit `confirmed` / `cancelled` / `not_found` / `ambiguous` verdict. A success screen is not proof; this is.
- **`tock_healthcheck`** — bridge status + the one-time pair code.

## Develop

```bash
npm install
npm run build     # tsc + esbuild bundle → dist/bundle.js
npm test          # vitest
```

Architecture and the reverse-engineered Tock surface are documented in [`docs/TOCK-API.md`](docs/TOCK-API.md).

## License

MIT

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