What is resy-mcp CLAUDE.md?

A set of instructions for using resy-mcp, an MCP server that connects an AI assistant to Resy’s private web-app API. It explains authentication, commands, tool names, and how the server is structured.

Use it when setting up, maintaining, or extending resy-mcp. It is especially relevant when working with Resy authentication or its reservation-management tools.

It gives coding agents the context needed to configure and use resy-mcp correctly. It also explains the available authentication paths and their order of priority.

How chrischall/resy-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to chrischall/resy-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/chrischall/resy-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/chrischall/resy-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/chrischall/resy-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/chrischall/resy-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/chrischall/resy-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/resy-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/chrischall/resy-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/resy-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5,265 This file is loaded in full into every session.

When invoked 5,265 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.05265	$0.05265
Opus 5.5	$0.02106	$0.02106
Sonnet 5.5	$0.01053	$0.01053
Haiku 4.5	$0.00526	$0.00526

Measured 22d ago against content hash 0344131a12c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

resy-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

resy-mcp AGENTS.md — 97% identical, 229 lines differ

CLAUDE.md · 228 lines

How it starts

The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.

resy-mcp

MCP server for Resy. Wraps Resy's private web-app API and exposes 14 resy_* tools over stdio: search venues, find slots, book/cancel reservations, manage favorites, and Priority Notify subscriptions.

Resy has no official public API. This server calls the same endpoints the resy.com web app calls. Use at your own discretion.

Auth (three paths, in priority order)

The client picks an auth path on demand:

RESY_AUTH_TOKEN — direct x-resy-auth-token override. Power users / CI. Skips everything else.
RESY_EMAIL + RESY_PASSWORD — POSTs /3/auth/password (form-encoded), caches the returned token.
fetchproxy bootstrap (Pattern B) — when neither of the above is set, calls POST https://api.resy.com/3/auth/refresh through the user's signed-in resy.com tab via @fetchproxy/server's FetchproxyServer.postJson. The browser auto-attaches the HttpOnly session cookies; the response body returns { token: "..." } which we use as both x-resy-auth-token and x-resy-universal-auth. After that, all API calls remain direct Node fetch — fetchproxy is invoked once per session bootstrap, never in the hot path. Opt-out with RESY_DISABLE_FETCHPROXY=1.

Why Pattern B (one bootstrap call, then direct fetch) instead of Pattern A (every call through fetchproxy)? Resy's session lives in HttpOnly cookies (localStorage / sessionStorage / IndexedDB are auth-empty). The page's only authenticated endpoint that returns a usable token in its response body is /3/auth/refresh — so we bridge that one call and run everything else directly.

Commands

npm run build          # tsc → dist/ + esbuild bundle → dist/bundle.js
npm test               # vitest, mocked fetch, no network
npm run test:watch     # watch mode
npm run test:coverage  # v8 coverage (text + html, no thresholds)
npm run smoke          # live read-only probe of /2/user, /3/user/reservations,
                       #   /3/user/favorites, /3/notify — needs real .env
npx tsc --noEmit       # typecheck only

Read the full file on GitHub · 228 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

22d ago Changed · +51 tokens per session 0344131a12c7
29d ago Changed · +1 lines · +555 tokens per session 24f1d62ff8e9
1mo ago Changed · +13 tokens per session ef749e3df7d1
1mo ago Changed · +367 tokens per session 0fc7322c9f11
1mo ago Changed · +1 tokens per session fc06dc58ac47
1mo ago Changed · +2 lines · +359 tokens per session 026b8deead8d
1mo ago Changed · +12 lines · +181 tokens per session 84b3441e8ed7
2mo ago Changed · +11 lines · +153 tokens per session db6787e1163d
2mo ago First seen · 202 lines · 3,585 tokens per session scan A 1f89cb8e66bf

Subscribe to this mod's changes

resy-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/resy-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 5,265 tokens to every session, about $0.0211 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

resy-mcp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
resy-mcp CLAUDE.mdchrischall/resy-mcp	Instructions file	2	3d ago	MIT	A	5,265	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

resy-mcp: Instructions file for Claude Code