io.github.chrischall/resy-mcp
NPM · RESY-MCP · SCANNED SEP 21
Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude
Available components
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 Security96
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 7 of 8 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 7 of 8 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
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
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1623 tokens (~108/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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% 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
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
{
"mcpServers": {
"chrischall-resy-mcp": {
"command": "npx",
"args": [
"-y",
"resy-mcp"
]
}
}
} {
"servers": {
"chrischall-resy-mcp": {
"command": "npx",
"args": [
"-y",
"resy-mcp"
]
}
}
} codex mcp add chrischall-resy-mcp -- npx -y resy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrischall-resy-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"resy-mcp"
],
"enabled": true
}
}
} openclaw mcp add chrischall-resy-mcp --command npx --arg -y --arg resy-mcp
mcp_servers:
chrischall-resy-mcp:
command: "npx"
args: ["-y", "resy-mcp"] {
"McpServers": {
"chrischall-resy-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"resy-mcp"
]
}
}
} assistant mcp add chrischall-resy-mcp -t stdio -c npx -a -y resy-mcp
{
"mcpServers": {
"chrischall-resy-mcp": {
"command": "npx",
"args": [
"-y",
"resy-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
- Known CVEs: pass → partial ▼ security
- Security disclosure: fail → unverified ▼ functional
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Dependency health: 1.00 → partial functional
- Package version: 1.1.0 → 1.1.1 functional
- 20 Sept 26 +8
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Stability: pass → 0.80 functional
- Package version: 1.0.0 → 1.1.0 functional
- 19 Sept 26 −10
- Stability: 0.97 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.14.4 → 1.0.0 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 0.14.3 → 0.14.4 functional
- 14 Sept 26 −15
- Stability: 0.80 → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.14.2 → 0.14.3 functional
- 13 Sept 26 −2
- Stability: pass → 0.80 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 21 Sept 2026 · Analysed npm/resy-mcp@1.1.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 | 2904926966 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a92642b56df32b132d73cb8674291fe4b3bb6e5b9e3b0f9e47736fe3651397dd0cca047062a29cee7af6253cba829683b343b1e60670d0d6ceb9f8057 |
Background: How many MCP packages publish verified provenance →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 ~281
Book a reservation. Composite tool: internally runs find-slots → get booking details → book. Confirm-gated: without confirm:true this returns a dry-run preview (venue, date, party size, the exact slot time that would be booked, and the payment card last-4) 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. Omit desired_time to take the first available slot. Uses the user's default payment method unless payment_method_id is supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_closest_time | boolean | – | When true, if your exact desired_time is unavailable the closest slot is booked instead of returning the available times to pick from. Default false: an unavailable desired_time never silently books… |
| confirm | boolean | – | Must be true to proceed. Without this, the tool returns a preview. |
| date | string | yes | YYYY-MM-DD |
| desired_time | string | – | HH:MM (24h) |
| lat | number | – | – |
| lng | number | – | – |
| party_size | integer | yes | – |
| payment_method_id | integer | – | – |
| venue_id | integer | yes | – |
No output schema declared.
No examples provided.
resy_cancel ~106
Cancel a Resy reservation by its resy_token (the rr://... identifier returned from resy_book or resy_list_reservations). Confirm-gated: without confirm:true this returns a dry-run preview (venue, date, time, party size, and any cancellation fee) and cancels nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed. Without this, the tool returns a preview. |
| 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 ~62
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 | – | – |
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.
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 91 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 1,623 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 21 September 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.