Tracking issue for the discovery-listing work. Full context, rationale, and the dead ends already ruled out live in docs/superpowers/specs/2026-07-30-directory-listings-design.md — read that before re-attempting anything here.
All items below are waiting on someone else. Nothing needs code.
Open pull requests
Glama — the only real blocker
Listed and claimed at https://glama.ai/mcp/servers/nimbus-agent/Nimbus, but no Glama release exists, so it shows "cannot be installed". Per Glama's methodology, a server without a working build "remains listed but isn't discoverable" — excluded from search and recommendations. So this listing currently does nothing for us, and it also gates #11216.
Verified locally, so these are ruled out as causes: the build spec is sound (their generated Dockerfile builds and serves all six tools when only the base image is changed), the checksum guard works, and the mcp-proxy wrapper does not disturb the server.
Once a build succeeds, Make Release (version 1.12.1) is a separate step — Deploy alone never clears "cannot be installed".
Note: the checked-in-Dockerfile route would bypass the admin UI entirely and let us pin both the base image and linux/amd64, but keeping a Dockerfile in this repo was declined — it invites "run Nimbus in Docker", which does not work, and it rots at every release. Do not re-litigate without a new reason.
PulseMCP
Do not attempt
modelcontextprotocol/docs → clients.mdx — the official client list is retired. modelcontextprotocol.io/clients redirects to the homepage and the repo is archived.- Official MCP Registry — needs a package on npm/PyPI/NuGet/Cargo/OCI/MCPB. Nimbus ships via Homebrew, winget and apt. Reaching it is a packaging decision, not a listing task.
janhq/awesome-local-ai — last push 2024-11-13; effectively abandoned.
Tracking issue for the discovery-listing work. Full context, rationale, and the dead ends already ruled out live in
docs/superpowers/specs/2026-07-30-directory-listings-design.md— read that before re-attempting anything here.All items below are waiting on someone else. Nothing needs code.
Open pull requests
[](https://glama.ai/mcp/servers/nimbus-agent/Nimbus)verification/cla-signedis green. Just awaiting maintainer merge.Glama — the only real blocker
Listed and claimed at https://glama.ai/mcp/servers/nimbus-agent/Nimbus, but no Glama release exists, so it shows "cannot be installed". Per Glama's methodology, a server without a working build "remains listed but isn't discoverable" — excluded from search and recommendations. So this listing currently does nothing for us, and it also gates #11216.
debian:trixie-slim: failed to resolve source metadata … context deadline exceededbaseImagetodebian:bookworm-slim— is not applicable: the option is visible in the admin dropdown but cannot be selected.Verified locally, so these are ruled out as causes: the build spec is sound (their generated Dockerfile builds and serves all six tools when only the base image is changed), the checksum guard works, and the
mcp-proxywrapper does not disturb the server.Once a build succeeds, Make Release (version
1.12.1) is a separate step — Deploy alone never clears "cannot be installed".Note: the checked-in-Dockerfile route would bypass the admin UI entirely and let us pin both the base image and
linux/amd64, but keeping aDockerfilein this repo was declined — it invites "run Nimbus in Docker", which does not work, and it rots at every release. Do not re-litigate without a new reason.PulseMCP
hello@pulsemcp.comrequesting a client listing. Their submit form now only redirects to the Official MCP Registry, which is servers-only, so email is the sole route for the client surface. Follow up if nothing appears within a week or so.Do not attempt
modelcontextprotocol/docs→clients.mdx— the official client list is retired.modelcontextprotocol.io/clientsredirects to the homepage and the repo is archived.janhq/awesome-local-ai— last push 2024-11-13; effectively abandoned.