Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/tock-mcp/issues.md or /mcp/tock-mcp/issues.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


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


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


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


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


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


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


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


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.