Reported issues for setlist-mcp

Pod holds 9 of 9 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 setlist-mcp.

Most discussed

Auto-review follow-ups for PR #121: docs(readme): npm test now typechecks before running vitest

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

🔴 Important

• package.json removes typecheck scripts that README.md documents as running — creates contradiction where documentation claims typecheck runs but actual scripts omit it

Checklist regenerated from the auto-review of 4b041d6 (run). Ticks survive later rounds, but a round that reviewed an older commit c

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

Auto-review follow-ups for PR #119: docs: npm test now typechecks before running vitest

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

🟡 Nits

• README.md line 62 should update npm test # vitest to npm test # tsc typecheck + vitest for consistency with CLAUDE.md

Checklist regenerated from the auto-review of 337e2a1 (run). Ticks survive later rounds, but a round that reviewed an older commit can still re-list something already fixed — check th

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

Auto-review follow-ups for PR #117: ci: typecheck in the test script, so CI actually checks types

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

🟡 Nits

• Documentation drift in CLAUDE.md lines 9 and 11: test command descriptions should mention the typecheck step

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

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

Auto-review follow-ups for PR #101: refactor(connector): retire the standalone Cloudflare Worker connector

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

🟡 Nits

• src/client.ts:16-18 and :46-50 still cite the retired Cloudflare Worker connector as the rationale for the fileURLToPath try/catch and the opts.apiKey constructor seam — re-justify generically or drop the guard

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

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

Auto-review follow-ups for PR #93: fix(web-client): single-flight the re-lift so concurrent writes can't race

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

🟡 Nits

• requireCookie() is not itself single-flighted, so a concurrent call reaching it outside relift() while the cookie is momentarily null can still trigger a duplicate resolveSessionCookie() bridge round-trip
• tests/tools/attendance.test.ts: mockInvalidate is a stale variable name left over from the renamed invalidateLiftedCookie() -> relift() method
• PR description's 'Doc' s

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

Auto-review follow-ups for PR #90: fix(attendance): re-lift an expired browser session instead of wedging

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

🟡 Nits

• src/tools/attendance.ts: SessionExpiredError class doc comment (~L20-26) still says the caller is told to re-pair the fetchproxy bridge, but the new SESSION_EXPIRED_MSG no longer says that
• src/web-client.ts: invalidateLiftedCookie()/requireCookie() mutate cookie state outside the write throttle's serialization, so concurrent setAttendance calls could race and cause one to ski

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

Auto-review follow-ups for PR #70: ci: deploy the connector Worker on release

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

🟡 Nits

• deploy-connector job in release-please.yml inherits broad workflow-level permissions (contents: write, pull-requests: write) instead of scoping down to contents: read like the workflow_dispatch stub does for the same reusable-workflow call

When addressing the review on #70, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred

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

Auto-review follow-ups for PR #55: feat(skill): add setlist.fm fpx/curl access skill

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

🟡 Nits

• attendance-write.md perl regex for locating the Wicket attendance control is order-dependent (requires title= before onclick= in the tag), unlike src/tools/attendance.ts's parseAttendance() which checks both independently — could misreport 'control not found' on real markup where title comes after onclick
• attendance-write.md's perl only unescapes & in the AJAX URL, wh

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

Most recent

Auto-review follow-ups for PR #62: feat: add hosted Cloudflare Worker connector (read-only v1)

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

🟡 Nits

• src/worker.ts is excluded from tsconfig.json so tsc/npm run build never type-checks it; add a tsconfig.worker.json + tsc --noEmit worker script to catch TS type errors that the runtime workers-pool test won't surface

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

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

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