pod
Other formats agents might prefer:
markdownjsonllms.txt

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

Reported issues for getyourguide-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 getyourguide-mcp.

Most discussed

npm publish of 1.0.0 is broken: tarball is missing dist/ (bin points at nonexistent dist/index.js)

Bug

getyourguide-mcp@1.0.0 on the npm registry does not contain the dist/ directory, even though:

  • package.json bin points at dist/index.js
  • files includes dist

Verified with npm pack getyourguide-mcp@1.0.0 — the tarball contains only:

package/LICENSE
package/.mcp.json
package/.claude-plugin/marketplace.json
package/package.json
package/.claude-plugin/plugin.json
package/server.json
package/README.md
package/skills/getyourguide/SKILL.md

So `npm install getyourgu

Read the thread · 2026-07-06 · closed · 2 comments

Auto-review follow-ups for PR #54: ci: sync the release-please stub from chrischall/workflows

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

🟡 Nits

  • Missing ci/github_actions release-notes label for ci: commit prefix

Checklist regenerated from the auto-review of 7a52cf4 (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

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

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

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

🔴 Important

  • Missing GYG_REQUEST_TIMEOUT_MS environment variable in mint.yaml
  • Incorrect egress host: partner.getyourguide.com is documentation-only, not actually fetched by the server

Checklist regenerated from the auto-review of b8d4985 (run). Ticks survive later rounds, but a round that reviewed an ol

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

Auto-review follow-ups for PR #29: build(deps): bump postcss out of the source-map path-traversal advisory

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

🟡 Nits

  • Missing release-notes label — apply dependencies to match build(deps): prefix

When addressing the review on #29, 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-25 · closed · external user · 1 comment

Auto-review follow-ups for PR #14: ci: switch the deferred-CI gate to status mode (pending ci-gated, green job)

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

🔴 Important

  • Coverage enforcement removed: switching from npm run test:coverage to npm test without explanation of how the documented 100% coverage requirement (CLAUDE.md line 16) is still enforced (.github/workflows/ci.yml:24)

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

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

Repo bootstrap: seed fleet pipeline labels

Throwaway issue used to auto-create the chrischall/workflows pipeline labels in this fresh repo (the Issues API creates labels on attach; there is no label-create surface available to the agent here). PR #3's review / review job failed with 'auto-review' not found because none of the fleet labels existed yet.

Labels seeded here: ready-to-merge, review-with-opus, release-ready, autorelease: pending, autorelease: tagged, ci, security, test, javascript, github_actions, `i

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

Most recent

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