SuperOps MCP

The materials explicitly require SUPEROPS_API_TOKEN. This is a sensitive credential and could allow unauthorized access to SuperOps PSA/RMM resources if exposed; however, requiring a service API token is standard for this type of tool, and no explicit credential abuse pattern is stated in the materials.

The objective checks show credentials are required, but no remote host is listed. Given the stated function of accessing SuperOps entities, it is reasonable to infer communication with SuperOps-related services. The materials do not disclose exact domains, data scope, or whether user prompts are forwarded, so egress transparency is limited, but there is no clear red flag indicating exfiltration to unrelated or unknown endpoints.

The system flags executes-code, meaning the MCP runs code/processes locally; this is a normal capability for MCP tools. The available materials do not indicate unusual system privileges or clearly unrelated high-risk actions, so this is best rated as caution.

The description mentions a 'local SQLite mirror,' indicating local storage of mirrored SuperOps data with corresponding read/write access. The materials do not specify which entities are mirrored, whether sensitive ticket/device/customer data is included, where it is stored, or retention behavior, so local data exposure and data minimization should be reviewed; however, there is no clear evidence of overbroad access beyond the stated function.

The source is an official registry entry and there is an auditable open-source repository with updates within the last year, all of which are positive signals. Although the license is not stated, community stars are low, and README detail is limited, these reduce transparency and maturity somewhat but do not amount to a high-risk supply-chain red flag.