Our main goal is to make Opsphere available directly through the Cursor Marketplace, alongside plugins such as Figma, Datadog and other officially published integrations.
In parallel, we also published the plugin on Cursor Directory with same name “opsphere”
However, we have noticed that it has remained in the “Verification requested” state for several weeks. During this time, we have continued improving the repository and have pushed multiple updates to the default branch (main), which is public, but those changes do not appear to be reflected in the Cursor Directory listing.
While we would appreciate any information regarding the verification process for Cursor Directory, our highest priority is the Marketplace publication.
If there are any adjustments, requirements, security recommendations, documentation changes, or architectural modifications needed for the plugin to be accepted into the Cursor Marketplace, we would greatly appreciate your guidance. We are happy to make any necessary changes to ensure the plugin fully complies with Cursor’s expectations and best practices.
Thank you very much for your time and for reviewing our submission. We look forward to your feedback and are excited about making Opsphere available to the Cursor community.
Hi @Connecting_Tech_Peop Thanks for the forum post! Can you reach out to [email protected] with this information? Let us know if you don’t hear back this week and we can escalate on our side
I really appreciate you flagging this with the directory team. However, I have received similar responses several times over the past two months, but unfortunately the situation has not progressed.
Our plugin was submitted at the end of May, and since then we have continuously improved it based on the feedback received. We have addressed the security review comments, updated the public repository, added the required documentation (Privacy Policy, Terms, SECURITY.md), and made multiple improvements to comply with the Marketplace requirements.
Despite all of this, we still don’t have any clear resolution or guidance on what is preventing the plugin from moving forward.
I’m attaching screenshots of the previous conversations so you can see the timeline. As you’ll notice, we’ve been following up regularly and every response has essentially been that it would be forwarded to another team, but we have never received a definitive answer.
What we really need at this point is one of the following:
Approval for publication.
A list of the remaining issues that need to be addressed.
Confirmation that the plugin has been rejected, together with the reasons.
Any of these outcomes would allow us to move forward. What is becoming difficult is remaining in an indefinite review state for almost two months without knowing what is actually blocking publication.
Our goal is to make Opsphere available through the Cursor Marketplace in the same way as plugins such as Figma, Datadog and other officially published integrations, and we’re fully committed to making any additional changes required to meet Cursor’s standards.
We would sincerely appreciate if someone from the Marketplace review team could take a final look at the submission and provide us with a concrete update.
Hi @Connecting_Tech_Peop We recently upgraded our marketplace publishing platform, can you please submit it for review here? https://cursor.directory/ Sorry for the additional steps. This is the new method and we are centralizing everything here!
However, since then its status has remained “Verification requested” (see attached screenshot), and it still doesn’t appear in Cursor’s built-in plugin search, so users can’t install it from the Marketplace.
Could you please help us understand what is still pending for the verification to be completed? If there’s anything we need to change or provide, we’d be happy to do it as soon as possible.
We’ve been trying to get Opsphere available for almost two months now, so we’d really appreciate your help in getting this resolved.
Please also check your email when you have a chance. I believe the directory is the canonical listing place going forward, replacing the marketplace. I think we are no longer accepting submissions generally for the marketplace.
Thank you for the clarification. I completely understand your decision regarding the Marketplace,
What I do need help with is understanding what’s happening with our Directory listing.
We deployed a new version of the plugin two days ago, on Monday, including a new subagent and several improvements, but none of those changes are reflected in Cursor Directory. At the same time, they do appear correctly in our Team Marketplace, which makes us think the repository updates are being picked up somewhere, but not by Cursor Directory.
Additionally, the plugin has been showing “Verification requested” for several weeks now (see attached screenshot), and we’re not sure whether that verification status is preventing the Directory from updating.
One question I have is whether this could be related to the fact that the plugin also exists in our Team Marketplace. Should we remove it from our Cursor Team Marketplace and keep it only in Cursor Directory, or are those two completely independent?
Could you please help us understand what is blocking the verification and why the latest version isn’t being reflected in the Directory?
Thank you again for your help—I really appreciate it.
