modelcontextprotocol / modelcontextprotocol/registry
Status updates via mcp-publisher consistently time out with 504 from nginx
Open
@pree-dew is already working on this.
Since Jul 14, 2026.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Summary
mcp-publisher status (v1.8.0) consistently fails with a 504 Gateway Time-out (nginx HTML error page) after ~60s when updating a server version's status against registry.modelcontextprotocol.io. Publishing new servers via POST /v0/publish works fine from the same environments.
Repro
From GitHub Actions (login github-oidc, org namespace):
./mcp-publisher status --status deleted --yes --all-versions \
--message "Superseded by io.contextstream/mcp" io.github.contextstream/mcp
Output:
This will update 1 version(s) of io.github.contextstream/mcp:
0.5.35: active → deleted
Error: server returned status 504: <html>
<head><title>504 Gateway Time-out</title></head>
...
- 5 attempts over ~1 hour on 2026-07-13 (19:33–20:35 UTC), all identical 504s after ~60s.
- Fetching the versions list (the step right before) succeeds each time, so reads are healthy; only the status-change call times out.
- Same-day publishes (
POST /v0/publish) from both DNS auth and github-oidc succeeded immediately, so this looks specific to the edit/status path (possibly a slow query or lock behind thePUT /v0/servers/{name}/versions/{version}handler exceeding the 60s proxy timeout).
Happy to provide timestamps/request details if useful.
🤖 Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.