Plugin stuck flagged after stale repository_clone_failed: lumify-sports-intelligence

Summary

Our Cursor Directory listing has been hidden pending manual review for weeks after a stale repository_clone_failed security-scan flag. Self-serve edit/resubmit did not clear it.

Plugin: https://cursor.directory/plugins/lumify-sports-intelligence
Repo: https://github.com/lumifyai/lumify (public)

Banner on the plugin page:

Flagged by the security agent. Hidden from the directory pending manual review.

Root cause

1. Listing was first submitted 2026-07-16 pointing at github.com/lumifyai/lumify.
2. That public repo did not exist until 2026-07-17, so the security agent's clone 404'd → repository_clone_failed.
3. Repo has been public + cloneable since then (verified repeatedly; current git ls-remote succeeds).
4. We edited/resubmitted to re-trigger the scan, but the listing remains flagged and hidden.

What we just fixed on the repo side (for a clean rescan)

Published Open Plugins layout at the public repo root so auto-detect works:

• .mcp.json — hosted MCP config matching the listing (https://lumify.ai/mcp + Bearer placeholder)
• .cursor-plugin/plugin.json — plugin manifest (lumify-sports-intelligence)

Remote MCP config (same as shown on the directory page):

{
  "mcpServers": {
    "lumify": {
      "url": "https://lumify.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Ask

Could an admin please either:

1. Clear the stale flag and re-run the security scan, or
2. Delete the stuck listing so we can submit a fresh one for the same repo/name

Happy to provide any IDs or owner-account details needed. Thanks!

Start by reviewing the linked repository's .mcp.json and .cursor-plugin/plugin.json, then trace the community-plugins security-scan and listing-review workflow. Done means the stale repository_clone_failed flag is cleared and the listing is rescanned, or the stuck listing is deleted as requested.