io.github.chrischall/resy-mcp
NPM · RESY-MCP
Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude
Available components
Last scanned (15 hours ago)
Scores higher than 72% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chrischall/resy-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2440 tokens (~162/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.3.5 → 1.4.1 functional
- Package version: 1.3.5 → 1.4.0 functional
- Package version: 1.3.3 → 1.3.5 functional
- 20 Oct 26 0
- Package version: 1.3.3 → 1.3.5 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Known CVEs: partial → pass ▲ security
- Stability: 0.90 → pass security
- Dependency health: partial → 1.00 functional
- Package version: 1.3.4 → 1.3.5 functional
- 16 Oct 26 −3
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → partial ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 1.00 → partial functional
- Stability: pass → 0.90 functional
- Package version: 1.3.3 → 1.3.4 functional
- 15 Oct 26 +44
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 1.3.0 → 1.3.3 functional
- 13 Oct 26 0
- Package version: 1.3.0 → 1.3.3 functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/resy-mcp@1.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chrischall/resy-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chrischall/resy-mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 3691534900 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1521c5b0a864d6d8af71d6f55b7057e8f83eba0e1ee6701a441986bdb76d09bd3e44f1e7cfea2068ea83b373f5fc8d784bb8f90071a7c4ac7fc073a2f |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
resy_add_favorite ~30
Add a venue to the user's favorites by venue_id.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_add_notify ~170
Subscribe to Priority Notify for a venue/date/party size. Resy emails you when a matching slot opens. time_start / time_end bound the window you're willing to accept (HH:MM, 24h). Resy's notify booking window only accepts near-term dates (~30 days out).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD (must be within Resy's notify window, ~30 days) |
| party_size | integer | yes | – |
| service_type_id | integer | – | Resy service type (2 = dining room, observed default) |
| time_end | string | – | Latest acceptable time, HH:MM. Defaults 21:00. |
| time_start | string | – | Earliest acceptable time, HH:MM. Defaults 18:00. |
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_book ~845
Book a reservation. Composite tool: internally runs find-slots → get booking details → book. It books ONLY the exact slot a preview showed. The first call returns a preview (the Resy account, venue, date, party size, the exact slot time that would be booked, its slot_type, the payment card last-4, and the slot's cancellation_policy / payment_terms — any no-show fee or deposit) and books nothing. Pass desired_time (HH:MM, 24-hour) to target a specific slot. If your exact desired_time is not available the tool does NOT auto-book a different time — it returns the available times so you can pick, unless you pass allow_closest_time:true (which previews the nearest slot). Omit desired_time to preview the first available slot. Resy can list several slots at one time with different seating types (Dining Room / Bar / Patio) and different fees; pass slot_type to target one. To book: on a client without a confirmation prompt the preview comes back with a confirmToken bound to that exact slot and its terms — after the user approves, call again with the same arguments plus the preview's time as desired_time and the confirmToken. On a client that can prompt, call again with the preview's time as desired_time, its slot_type and its terms_token, and the user is asked to confirm. If that slot is gone, or its seating type or cancellation/payment terms changed since the preview, nothing is booked and a fresh preview is returned. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Before booking, it checks your existing reservations and refuses if you already hold one at this venue on this date (e.g. an earlier call that timed out but went through); pass allow_duplicate:true to book another anyway. Uses the user's default payment method unless payment_method_id is supplied (it must be one of the saved cards from resy_li…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_closest_time | boolean | – | When true, if your exact desired_time is unavailable the preview selects the closest slot instead of returning the available times to pick from. It never books on its own: book with that slot's time… |
| allow_duplicate | boolean | – | When true, book even if you already hold a reservation at this venue on this date. Default false: the booking refuses and lists the existing reservation, so a retry after a timed-out booking cannot b… |
| confirmToken | string | – | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se… |
| date | string | yes | YYYY-MM-DD |
| desired_time | string | – | HH:MM (24h) |
| lat | number | – | – |
| lng | number | – | – |
| party_size | integer | yes | – |
| payment_method_id | integer | – | – |
| slot_type | string | – | Seating type (e.g. 'Dining Room', 'Bar', 'Patio'), matched case-insensitively. Only slots of this type are considered. On a client that can prompt it is required to book — pass the preview's slot_typ… |
| terms_token | string | – | The preview's terms_token. It fingerprints the slot's seating type and cancellation/payment terms; if they changed since the preview, the call re-previews instead of booking. Required to book on a cl… |
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_cancel ~271
Cancel a Resy reservation by its resy_token (the rr://... identifier returned from resy_book or resy_list_reservations). The confirmation preview shows the Resy account, venue, date, time, party size, and any cancellation fee. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Once confirmed, the result carries `cancelled` (boolean: true only when the cancellation is confirmed) and `outcome` ("cancelled", "not_cancelled", or "unknown"). On "unknown", `cancelled` is false but the reservation MAY have been cancelled — check resy_list_reservations before retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmToken | string | – | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se… |
| resy_token | string | yes | rr://... reservation identifier |
No output schema declared.
No examples provided.
resy_find_slots ~82
List available reservation slots at a specific venue for a date + party size. Returns slot config_tokens suitable for booking. Tokens expire quickly; book soon after fetching.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD |
| lat | number | – | – |
| lng | number | – | – |
| party_size | integer | yes | – |
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_get_profile ~120
Get the authenticated Resy user's profile (name, email, phone, booking count, member-since date). Payment method IDs are not exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full"… |
No output schema declared.
No examples provided.
resy_get_venue ~31
Get full details for a single Resy venue by id.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_healthcheck Verify credentials and upstream reachability ~101
Resolves the credential the way real tools do, then makes one authenticated request to api.resy.com. Reports which source supplied the credential, whether api.resy.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.resy.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resy_list_favorites ~104
List the user's favorited Resy venues ("hit list").
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full"… |
No output schema declared.
No examples provided.
resy_list_notify ~106
List Priority Notify subscriptions — tables you are waiting for when reservations open up.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full"… |
No output schema declared.
No examples provided.
resy_list_payment_methods ~131
List the user's saved payment methods on Resy. Returns id, brand, last four digits, expiry, and is_default. The id can be passed as payment_method_id to resy_book.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full"… |
No output schema declared.
No examples provided.
resy_list_reservations ~150
List the user's Resy reservations. Defaults to upcoming; pass scope="past" or "all" to broaden. Each result includes the resy_token needed for cancellation, plus occasion/special_request/cancellability.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
| view | string | – | "full" (default) returns each reservation as JSON; "brief" returns one line per reservation: <venue> <HH:MM>, party of <n> — <YYYY-MM-DDTHH:MM or "no date"> — <booked|past>, inside the untrusted-data… |
No output schema declared.
No examples provided.
resy_remove_favorite ~30
Remove a venue from the user's favorites by venue_id.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_remove_notify ~46
Cancel a Priority Notify subscription by notify_id. The tool looks up the full spec from resy_list_notify internally — no other input needed.
| Name | Type | Req | Description |
|---|---|---|---|
| notify_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_search_venues ~223
Search Resy for restaurants with availability. Returns venues including any bookable slot tokens for the requested date + party size. Defaults to NYC geo if lat/lng omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Desired date YYYY-MM-DD |
| lat | number | – | Latitude (default 40.7128 NYC) |
| limit | integer | – | Max venues (default 20) |
| lng | number | – | Longitude (default -73.9876 NYC) |
| party_size | integer | yes | Number of guests |
| query | string | – | Venue name or keyword |
| radius_meters | integer | – | Search radius in meters (default 16100) |
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full"… |
No output schema declared.
No examples provided.
How do I install the io.github.chrischall/resy-mcp server?
io.github.chrischall/resy-mcp runs locally as an npm package, launched with npx -y resy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · resy-mcp
claude mcp add chrischall-resy-mcp -- npx -y resy-mcp
What is the io.github.chrischall/resy-mcp server?
io.github.chrischall/resy-mcp is listed in the public MCP registry as io.github.chrischall/resy-mcp. Resy reservation management, search, book, cancel, favorites, and Priority Notify for Claude. This page covers its npm package (resy-mcp).
Is the io.github.chrischall/resy-mcp server safe to use?
io.github.chrischall/resy-mcp scores 82 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.chrischall/resy-mcp server expose?
io.github.chrischall/resy-mcp exposes 15 tools: resy_get_profile, resy_list_payment_methods, resy_healthcheck, resy_search_venues, resy_find_slots, and 10 more. Their descriptions and schemas cost roughly 2,440 tokens of context every time the server is loaded.
Is the io.github.chrischall/resy-mcp server still maintained?
io.github.chrischall/resy-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.chrischall/resy-mcp server under?
io.github.chrischall/resy-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.