DeployMonster security scan failed; please rerun or review manually

Open
#539 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github, json, typescript
Domain
devtools

Research direction

The issue asks an admin to rerun or inspect DeployMonster’s security scan, but it identifies no repository files, tests, or implementation entry point; the plugin has no public implementation repository. Start by locating the scan workflow and its admin rescan path in the community-plugins repository. Done means identifying the actionable scan error or successfully rerunning the scan so the listing can proceed through review.

Written by the indexing model from the issue text.

Description

Hi,

Could an admin inspect and rerun the failed security scan for DeployMonster?

Listing: https://cursor.directory/plugins/deploymonster

The page says "Scan failed. An admin will re-run it shortly." and the plugin remains unpublished and hidden. Verification has already been requested. We saved the existing configuration again, including a formatting-only update, but the listing still shows the scan error. The owner UI does not expose the underlying error or a rescan button.

This is an inline remote MCP component with no public implementation repository. Its configuration is:

{
  "mcpServers": {
    "deploymonster": {
      "url": "https://mcp.deploymonster.app"
    }
  }
}

The hosted service requires OAuth. An independent live check passed token refresh, initialization, tools/list (35 tools), and get_profile. It is active in the official MCP Registry as app.deploymonster/deploymonster and published in the Claude directory:

Please rerun the security scan or let us know the actionable scan error. We are not requesting a bypass of the security review.

Thanks,
Edi
Exevio / DeployMonster

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.