Publish returns "Plugin not found" on any submission whose first scan failed with "Cursor SDK startup failed: Invalid User API Key"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authorization, backend
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 4k
- Forks
- 671
- Avg merge
- 7m
- Merged PRs (30d)
- 32
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from cursor/community-plugins
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cursor/community-plugins#583 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
cursor/community-plugins#578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
cursor/community-plugins#576 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
cursor/community-plugins#572 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
cursor/community-plugins#567 · 4 comments ·
Maintainers usually reply within 1 day
All issues in cursor/community-plugins
Similar issues
-
[UI] Guard webApis against undefined window in SSR environmentsPossibly taken @madhavzanwar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
headroomlabs-ai/headroom#4992 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paperclipai/paperclip#22575 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#34502 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug frontend good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
nikhilb2/simple_invoicing#935 ·