pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for resy-mcp

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to resy-mcp.

Most discussed

Auto-review follow-ups for PR #149: feat: add resy_healthcheck

Tracking auto-review follow-ups for #149 (verdict: warn).

🟡 Nits

  • Misplaced JSDoc in src/client.ts: describeCredential()'s doc comment (lines 212-226) was inserted between mintToken's pre-existing JSDoc (193-211) and the mintToken() method (234), orphaning mintToken's documentation

Checklist regenerated from the auto-review of 5897d21 (run). Ticks survive later rounds, bu

Read the thread · 2026-08-30 · closed · outside contributor · 1 comment

Auto-review follow-ups for PR #143: docs: list the cache env vars in server.json and .env.example

Tracking auto-review follow-ups for #143 (verdict: fail).

🔴 Important

  • RESY_TOKEN_CACHE description exceeds 100 character limit

Checklist regenerated from the auto-review of 9d5c3dd (run). Ticks survive later rounds, but a round that reviewed an older commit can still re-list something already fixed — check that SHA before redoing an item.

When addressing the review on #

Read the thread · 2026-08-27 · closed · outside contributor · 1 comment

Auto-review follow-ups for PR #135: feat: cache the minted auth token so a restart skips re-minting

Tracking auto-review follow-ups for #135 (verdict: pass).

🟡 Nits

  • CLAUDE.md's Architecture file tree and Environment env-var table were not updated for this PR (missing src/token-cache.ts entry and RESY_TOKEN_CACHE/RESY_TOKEN_FILE env vars, both of which mint.yaml already documents)

Checklist regenerated from the auto-review of b7d13e5 (run). Ticks survive later rounds, b

Read the thread · 2026-08-26 · closed · outside contributor · 0 comments

Auto-review follow-ups for PR #128: chore: declare a mint.yaml hosting manifest

Tracking auto-review follow-ups for #128 (verdict: warn).

🟡 Nits

  • mint.yaml egress.allow includes resy.com, contradicting its own comment that only hosts the server process actually fetches should be listed — grep shows only api.resy.com is ever literally fetched
  • .mcpbignore's new mint.yaml entry (line 74) is redundant with the existing .yaml/.yml globs (lines 36-37)

Checklist regenerated from the auto-review of 149054b ([run](ht

Read the thread · 2026-08-25 · closed · outside contributor · 0 comments

Auto-review follow-ups for PR #107: ci: convert to chrischall/workflows reusable pipeline

Tracking auto-review follow-ups for #107 (verdict: fail).

🔴 Important

  • release-please.yml drops skill-path: skills/resy/SKILL.md input to mcp-publish composite action, risking the documented two-skill auto-discovery hard-failure on the next release publish

When addressing the review on #107, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review fo

Read the thread · 2026-07-27 · closed · outside contributor · 1 comment

Auto-review follow-ups for PR #85: fix: confirm-gate resy_book/resy_cancel and stop silent wrong-time booking

Tracking auto-review follow-ups for #85 (verdict: warn).

🟡 Nits

  • tests/tools/reservations.test.ts: missing test for resy_book preview when desired_time is omitted (first-slot fallback, requested_time:null path is untested)

When addressing the review on #85, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up convention in CLAUDE.md.

Read the thread · 2026-07-07 · closed · outside contributor · 0 comments

Most recent

The remaining reports are on the project's issue tracker.