Admin clear: stale repository_clone_failed on yieldhuntereth-yieldsentineleth (Source fixed to yieldhunter-connect)

[agentsherpa]

Request

Please clear / re-scan the Cursor Directory listing after a Source URL fix. Security agent still shows a stale repository_clone_failed against a repo that never existed.

Listing

• Directory URL: https://cursor.directory/plugins/yieldhuntereth-yieldsentineleth
• Title: yieldhunter.eth + yieldsentinel.eth
• Status: Flagged by the security agent; unpublished/hidden pending manual review

What went wrong

Initial submit used a bad Source URL:

• ❌ https://github.com/agentsherpa/yieldhunter (404 — repo does not exist)

We edited the listing and set Source to the correct public repo:

• ✅ https://github.com/agentsherpa/yieldhunter-connect (public; git ls-remote works; contains plugin.json + mcp.json + MIT)

After edit+resubmit, the security banner still cites the old agentsherpa/yieldhunter 404 and keeps the listing unpublished.

Ask

Please clear the stale flag / re-run the security scan against agentsherpa/yieldhunter-connect so the listing can become publishable (or tell us if another action is required).

Notes

• No payment involved
• Thin public connect repo only (intentional); private agent code stays private
• Sibling MCP: https://github.com/agentsherpa/yieldsentinel-connect (not the Directory Source)

Thanks!

[agentsherpa]

Follow-up after the security CLEAR:

• Direct listing is live: https://cursor.directory/plugins/yieldhuntereth-yieldsentineleth (yieldhunter.eth + yieldsentinel.eth)
• Source URL is now the correct public repo: https://github.com/agentsherpa/yieldhunter-connect
• Stale security / clone-failed banners are gone

Search on cursor.directory for yieldhunter / yieldsentinel still returns no hits (checked 8 Sep). Could you trigger a search reindex for this listing if that’s helpful?

No second listing planned — just this one quiet ping. Thanks.