Publish returns "Plugin not found" on any submission whose first scan failed with "Cursor SDK startup failed: Invalid User API Key"

Open
#529 3 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Submit an MCP server at the community plugin submission form.
    • Repo: https://github.com/adrianpeticila/grai
    • Package: grai-mcp on PyPI, version 0.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
  2. Let the initial scan run. It fails and the submission records:
    flag_summary: "Cursor SDK startup failed: Invalid User API Key"
  3. Open the submission and click Publish.
  4. 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.ts and delete-plugin.ts both 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-scans runs on status = 'processing' but skips status = '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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/community-plugins

All issues in cursor/community-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.