Other formats agents might prefer:
markdownjsonllms.txt

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

Reported issues for tock-mcp

Pod holds 8 of 8 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 tock-mcp.

Most discussed

Auto-review follow-ups for PR #59: feat(verify): add tock_verify_reservation, an executable booking check

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

🟡 Nits

  • SKILL.md line 100 ("Only tock_list_reservations / tock_get_profile require a signed-in tab") wasn't updated to include the new tock_verify_reservation, which also requires sign-in

When addressing the review on #59, 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 conventi

Read the thread · 2026-08-10 · closed · external user · 0 comments

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

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

🔴 Important

  • release-please.yml drops the required skill-path: skills/tock-mcp/SKILL.md input to the mcp-publish action, reintroducing the documented 'Multiple skills/*/SKILL.md found' publish-job failure

When addressing the review on #40, 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

Read the thread · 2026-07-27 · closed · external user · 1 comment

Auto-review follow-ups for PR #25: feat(skill): add tock fpx access skill

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

🟡 Nits

  • requests.md §6 (line 141) reads /tmp/tock-reservations-response.json, a file §5's command never writes (it pipes the fpx response straight into jq) — running §5 then §6 verbatim fails with 'No such file or directory'

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

Read the thread · 2026-07-13 · closed · external user · 0 comments

Auto-review follow-ups for PR #21: chore(main): release 0.2.0

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

🔴 Important

  • CHANGELOG.md: Remove duplicate entries from 0.1.0 section (lines 37, 42, 47–48, 53 contain features/fixes that belong only to 0.2.0)

When addressing the review on #21, 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-12 · closed · external user · 0 comments

Auto-review follow-ups for PR #21: chore(main): release 0.1.0

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

🔴 Important

  • Duplicate changelog entries for version 0.1.0 — release config forces same version instead of incrementing

When addressing the review on #21, 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-12 · closed · external user · 0 comments

Auto-review follow-ups for PR #13: refactor: adopt scrape isCloudflareChallenge + UpstreamHttpError

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

🟡 Nits

  • UpstreamHttpError re-export in src/client.ts is unused dead code — remove it or update its comment to reflect it’s an intentional affordance rather than for 'existing' import sites

When addressing the review on #13, 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 conve

Read the thread · 2026-07-07 · closed · external user · 0 comments

Auto-review follow-ups for PR #7: docs: finalize booking-protocol spec (auth-header findings)

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

🔴 Important

  • docs/TOCK-API.md lines 161–164: stale duplicate ### Step 2 — price check heading and description not removed when new Step 2 block was inserted at lines 172–174

When addressing the review on #7, 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-06 · closed · external user · 0 comments

Auto-review follow-ups for PR #5: docs+feat: Tock booking-protocol spec + protobuf codec

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

🟡 Nits

  • src/protobuf.ts:51,61 — num << 3 integer overflow for field numbers ≥ 2²⁸; use BigInt(num) << 3n instead
  • docs/TOCK-API.md:243 — 'Header hints' section duplicated verbatim; delete the second occurrence

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

Read the thread · 2026-07-05 · closed · external user · 0 comments

Most recent

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