Publish returns "Plugin not found" on any submission whose first scan failed with "Cursor SDK startup failed: Invalid User API Key"
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 15/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- authorization, backend
Línea de trabajo
The payload points to three places: toggle-plugin-listing.ts and delete-plugin.ts, where the row-level-security check on mutations appears to differ from the ownership check used for reads, and recover-stuck-scans, which picks up status = 'processing' but skips status = 'error'. Start by comparing the RLS policy on those mutations with the read policy, then check whether the error status is handled. Done means a failed scan can be re-queued or the record can be deleted, and the ownership rules match across reads and writes. Reproducing this needs access to the submission backend, so confirm that with a maintainer first.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
A submission that fails its first scan is stuck permanently. Publish returns Plugin not found, and there is no visible way to re-run the scan from the dashboard. The scan error itself is server side.
Steps to reproduce
- Submit an MCP server at the community plugin submission form.
- Repo:
https://github.com/adrianpeticila/grai - Package:
grai-mcpon PyPI, version0.1.2 - Official registry entry:
io.github.adrianpeticila/grai-mcp - Transport: stdio
- Command:
uvx --from grai-mcp grai-gate-mcp - Submitted:
2026-11-10T20:53:00Z
- Repo:
- Let the initial scan run. It fails and the submission records:
flag_summary: "Cursor SDK startup failed: Invalid User API Key" - Open the submission and click Publish.
- The response is
Plugin not found.
Expected
Either the submission stays in a state where the scan can be re-run, or Publish works once the scan passes. Right now neither path exists, and the record cannot even be deleted.
Actual
Plugin not found on Publish, on every retry, across reloads and sessions. The submission is orphaned: it exists in my account, it cannot be published, and it cannot be removed. No request ID or error code is surfaced in the UI to quote back.
Why this is not a package problem
The server runs standalone with zero dependencies and a clean stdio handshake:
uvx --from grai-mcp grai-gate-mcp
Verified against grai-mcp==0.1.2: initialize returns serverInfo grai-gate version 0.1.2, tools/list returns the three tools, grai_score_draft returns a score and the failed rules. The package has no runtime deps (dependencies = [] in pyproject.toml), no auth of its own, and no network calls on startup. The failing check references a Cursor SDK API key, which is not something the submission provides or is asked for. The same package is active in the official MCP Registry (io.github.adrianpeticila/grai-mcp, version 0.1.2), so the metadata is parseable.
Two things I hit while debugging, possibly the same root cause
toggle-plugin-listing.tsanddelete-plugin.tsboth return a row-level-security denial for a record that is visible to the caller in the dashboard. A submission that cannot be toggled or deleted suggests the RLS policy on those mutations does not match the ownership check used for reads.recover-stuck-scansruns onstatus = 'processing'but skipsstatus = 'error', so a scan that errors out is never picked up again. From the outside, that looks identical to a listing that was silently dropped.
Impact
Any server whose first scan hits a transient or server-side error loses the submission permanently and has to start over, with no diagnostic to act on. That is the state of grai-cadence-gate since 2026-11-10T20:53:00Z.
Ask
Triage the orphaned record so it can be re-scanned or deleted. If the API key failure is on your side, a dashboard action to re-queue the scan would unblock it without manual intervention.
- Lenguaje dominante
- TypeScript
- Estrellas
- 4k
- Forks
- 674
- Merge medio
- 8 min
- PR fusionados (30 d)
- 28
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cursor/community-plugins
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
cursor/community-plugins#572 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
cursor/community-plugins#567 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 73/100
cursor/community-plugins#543 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 66/100
cursor/community-plugins#518 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
cursor/community-plugins#516 ·
Los mantenedores suelen responder en 1 día
Todos los issues de cursor/community-plugins
Issues similares
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
truapi-release
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
paritytech/product-sdk#529 ·
Los mantenedores suelen responder en 1 día
-
Add: Mansudae TVAbiertoapproved check:passed streams:add
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
[Perf] Canvas layer composition is quadratic: splitRenderLayers re-copies the node array per nodeAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
devlikeapro/waha#2369 ·
Los mantenedores suelen responder en 5 días