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

未关闭
#529 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
4k
派生
674
平均合并
8 分钟
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cursor/community-plugins 的其他 Issue

查看 cursor/community-plugins 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。