io.github.chrischall/resy-mcp
Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude
The current version, v0.14.3, was published to the official MCP registry on 2026-09-14. It is distributed as resy-mcp on npm, filed under Search by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using io.github.chrischall/resy-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions found”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-14).
Contracts can change after screening, with no version bump. The gate pins io.github.chrischall/resy-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for io.github.chrischall/resy-mcp](https://mcpindex.ai/server/io-github-chrischall-resy-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-chrischall-resy-mcp">Independent trust record for io.github.chrischall/resy-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-chrischall-resy-mcp)<a href="https://mcpindex.ai/server/io-github-chrischall-resy-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-chrischall-resy-mcp" alt="mcpindex verdict" height="20" /></a>RESY_EMAILYour Resy account email. Optional — leave unset to use the fetchproxy browser bridge instead.
RESY_PASSWORDYour Resy account password. Optional — leave unset to use the fetchproxy browser bridge instead.
RESY_AUTH_TOKENPre-obtained x-resy-auth-token. Overrides email/password and the fetchproxy bridge. Power users / CI only.
RESY_DISABLE_FETCHPROXYSet to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN).
RESY_API_KEYPin the api key, beating both the key captured from the live site and the compiled-in default. Rotation does not require it: the key is captured and cached automatically.
RESY_TOKEN_CACHESet to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled.
RESY_TOKEN_FILEAbsolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json.
RESY_API_KEY_FILEAbsolute path for the api-key cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/api-key.json. Holds the bare key captured from the live site, which takes precedence over the compiled-in default.
RESY_CAPTURE_TIMEOUTSeconds to wait for the signed-in page to make an API call the bridge can read the auth token from. Defaults to 30. Capture resolves on the next matching request, so an idle tab needs a longer window than a busy one.
RESY_WS_PORTPort for the fetchproxy bridge. The whole fleet shares 37149 (the Transporter extension dials it), so override only for local development, test isolation, or a hosted bridged registration — this is the variable to name in the registration's bridgePortEnv.
Trend, stats & insight search across PSFK expert graphs with citable sources.
Connect AI agents to ProductNow's context engine to search, create, review, and act.
Unofficial Thumbtack MCP — search local service pros, read profiles, ratings and reviews