pod
Other formats agents might prefer:
markdownjsonllms.txt

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

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

Most discussed

Release verification failed for v1.3.2

Release verification (release-verify.yml) failed for tag v1.3.2.

Run: https://github.com/smaniches/uniprot-mcp/actions/runs/30448748220

One or more of {PyPI, GitHub Release assets, SLSA provenance, Zenodo DOI} did not land within the timeout. Inspect the failing step in the run above, then either re-trigger publication or patch the release chain before the next tag.

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

Nightly integration failed on 2026-06-29

The live UniProt integration suite failed. This often means UniProt changed its response shape. See run 28354832969.

Read the thread · 2026-06-29 · closed · outside contributor · 1 comment

Release verification failed for v1.2.0

Release verification (release-verify.yml) failed for tag v1.2.0.

Run: https://github.com/smaniches/uniprot-mcp/actions/runs/27657470277

One or more of {PyPI, GitHub Release assets, SLSA provenance, Zenodo DOI} did not land within the timeout. Inspect the failing step in the run above, then either re-trigger publication or patch the release chain before the next tag.

Read the thread · 2026-06-17 · closed · outside contributor · 1 comment

Release verification failed for v1.1.10

Release verification (release-verify.yml) failed for tag v1.1.10.

Run: https://github.com/smaniches/uniprot-mcp/actions/runs/27635191068

One or more of {PyPI, GitHub Release assets, SLSA provenance, Zenodo DOI} did not land within the timeout. Inspect the failing step in the run above, then either re-trigger publication or patch the release chain before the next tag.

Read the thread · 2026-06-16 · closed · outside contributor · 1 comment

Nightly integration failed on 2026-05-30

The live UniProt integration suite failed. This often means UniProt changed its response shape. See run 26677019134.

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

Nightly integration failed on 2026-04-26

The live UniProt integration suite failed. This often means UniProt changed its response shape. See run 24949960382.

Read the thread · 2026-04-26 · closed · outside contributor · 1 comment

Most recent

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