SuperOps

OCI · GHCR.IO/WYRE-TECHNOLOGY/SUPEROPS-MCP:V1.6.6 · SCANNED AUG 22

MCP server for SuperOps unified PSA+RMM — clients, tickets, assets, and more.

Available components

oci · ghcr.io/wyre-technology/superops-mcp:v1.6.6 41

41 41 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Install-script risk not yet assessed.Unverified
Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (Apache-2.0).Pass
Actively maintained (last published 1 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability85

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 1545 tokens (~70/item across 22 items; 21 tools + 1 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/wyre-technology/superops-mcp:v1.6.6

Claude Codex opencode Hermes Other

# add to Claude Code

claude mcp add wyre-technology-superops-mcp -- docker run --rm -i ghcr.io/wyre-technology/superops-mcp:v1.6.6

# add to Codex CLI

codex mcp add wyre-technology-superops-mcp -- docker run --rm -i ghcr.io/wyre-technology/superops-mcp:v1.6.6

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-superops-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/superops-mcp:v1.6.6"
      ],
      "enabled": true
    }
  }
}

# ~/.hermes/config.yaml

mcp_servers:
  wyre-technology-superops-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/superops-mcp:v1.6.6"]

// mcp.json

{
  "mcpServers": {
    "wyre-technology-superops-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/superops-mcp:v1.6.6"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

20 Aug 26 41

First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/superops-mcp:v1.6.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	oci
Reason	No attestation published

MCP tools · 21 exposed · ~1,527 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

superops_assets_get ~38

Get detailed information for a specific asset including hardware, OS, and network details.

Input Output Examples

Name	Type	Req	Description
assetId	string	yes	The unique asset ID

No output schema declared.

No examples provided.

superops_assets_list ~115

List assets (endpoints) in SuperOps.ai RMM. Can filter by status, platform, or client.

Input Output Examples

Name	Type	Req	Description
clientId	string	–	Filter by client account ID
cursor	string	–	Pagination cursor for fetching next page
max	number	–	Maximum number of results (default: 100, max: 500)
platform	string	–	Filter by platform: Windows, macOS, or Linux
status	string	–	Filter by status: Online, Offline, or Maintenance

No output schema declared.

No examples provided.

superops_assets_patches ~71

Get patch status and pending patches for a specific asset.

Input Output Examples

Name	Type	Req	Description
assetId	string	yes	The unique asset ID
severity	array	–	Filter by severity levels: Critical, Important, Moderate, Low
status	string	–	Filter patches by status: Pending, Installed, or Failed

No output schema declared.

No examples provided.

superops_assets_software ~62

Get the software inventory for a specific asset.

Input Output Examples

Name	Type	Req	Description
assetId	string	yes	The unique asset ID
max	number	–	Maximum number of results (default: 100)
search	string	–	Search term to filter software by name

No output schema declared.

No examples provided.

superops_clients_get ~37

Get detailed information for a specific client by their account ID.

Input Output Examples

Name	Type	Req	Description
accountId	string	yes	The unique account ID of the client

No output schema declared.

No examples provided.

superops_clients_list ~105

List clients (accounts) in SuperOps.ai. Can filter by status, stage, or paginate through results.

Input Output Examples

Name	Type	Req	Description
cursor	string	–	Pagination cursor for fetching next page
max	number	–	Maximum number of results (default: 50, max: 500)
stage	string	–	Filter by stage: Lead, Prospect, Customer, or Churned
status	string	–	Filter by status: Active, Inactive, or Archived

No output schema declared.

No examples provided.

superops_clients_search ~59

Search for clients by name or email domain. Returns matching clients with basic information.

Input Output Examples

Name	Type	Req	Description
max	number	–	Maximum number of results (default: 20)
query	string	yes	Search term to find clients by name or email domain

No output schema declared.

No examples provided.

superops_custom_mutation ~59

Run a custom GraphQL mutation against the SuperOps.ai API. For advanced write operations not covered by standard tools.

Input Output Examples

Name	Type	Req	Description
mutation	string	yes	The GraphQL mutation string
variables	object	–	Variables to pass to the mutation

No output schema declared.

No examples provided.

superops_custom_query ~58

Run a custom GraphQL query against the SuperOps.ai API. For advanced use cases not covered by standard tools.

Input Output Examples

Name	Type	Req	Description
query	string	yes	The GraphQL query string
variables	object	–	Variables to pass to the query

No output schema declared.

No examples provided.

superops_navigate ~141

Discover available SuperOps.ai tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	The domain to explore: - clients: Client/company management - list, get, search accounts and company information - tickets: Ticket management - list, get, create tickets and manage support workflow -…

No output schema declared.

No examples provided.

superops_status ~16

Show credentials status and available domains

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

superops_technicians_get ~35

Get detailed information for a specific technician by their ID.

Input Output Examples

Name	Type	Req	Description
technicianId	string	yes	The unique technician ID

No output schema declared.

No examples provided.

superops_technicians_groups ~38

List technician groups/teams in SuperOps.ai.

Input Output Examples

Name	Type	Req	Description
max	number	–	Maximum number of results (default: 50)

No output schema declared.

No examples provided.

superops_technicians_list ~93

List technicians (agents) in SuperOps.ai. Can filter by active status or team.

Input Output Examples

Name	Type	Req	Description
activeOnly	boolean	–	Show only active technicians (default: true)
cursor	string	–	Pagination cursor for fetching next page
max	number	–	Maximum number of results (default: 50, max: 500)
teamId	string	–	Filter by team/group ID

No output schema declared.

No examples provided.

superops_test_connection ~22

Test the connection to SuperOps.ai API using configured credentials.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

superops_tickets_add_note ~69

Add a note to a ticket. Can be internal or public (visible to client).

Input Output Examples

Name	Type	Req	Description
content	string	yes	Note content
isPublic	boolean	–	Whether the note is visible to the client (default: false)
ticketId	string	yes	The ticket ID

No output schema declared.

No examples provided.

superops_tickets_create ~113

Create a new ticket in SuperOps.ai.

Input Output Examples

Name	Type	Req	Description
categoryName	string	–	Service category name
clientId	string	yes	Client account ID
description	string	–	Detailed description of the issue
priority	string	–	Ticket priority: Low, Medium, High, or Critical
requesterEmail	string	–	Email of the person reporting the issue
subject	string	yes	Ticket subject/title
techGroupName	string	–	Name of the technician group to assign

No output schema declared.

No examples provided.

superops_tickets_get ~34

Get detailed information for a specific ticket by its ID.

Input Output Examples

Name	Type	Req	Description
ticketId	string	yes	The unique ticket ID

No output schema declared.

No examples provided.

superops_tickets_list ~148

List tickets in SuperOps.ai. Can filter by status, priority, client, or assignee.

Input Output Examples

Name	Type	Req	Description
assigneeId	string	–	Filter by assigned technician ID
clientId	string	–	Filter by client account ID
cursor	string	–	Pagination cursor for fetching next page
max	number	–	Maximum number of results (default: 50, max: 500)
priority	array	–	Filter by priority(ies): Low, Medium, High, Critical
status	array	–	Filter by status(es): Open, In Progress, Pending, Resolved, Closed
unassigned	boolean	–	Show only unassigned tickets

No output schema declared.

No examples provided.

superops_tickets_log_time ~92

Log time spent on a ticket.

Input Output Examples

Name	Type	Req	Description
billable	boolean	–	Whether the time is billable (default: true)
description	string	–	Description of work performed
duration	number	yes	Time spent in minutes
ticketId	string	yes	The ticket ID
workType	string	–	Type of work (e.g., Remote Support, On-site, Phone)

No output schema declared.

No examples provided.

superops_tickets_update ~122

Update an existing ticket - change status, priority, assignment, or add resolution.

Input Output Examples

Name	Type	Req	Description
assigneeId	string	–	ID of technician to assign
priority	string	–	New priority: Low, Medium, High, Critical
resolution	string	–	Resolution notes (for resolving/closing tickets)
status	string	–	New status: Open, In Progress, Pending, Resolved, Closed
techGroupName	string	–	Name of technician group to assign
ticketId	string	yes	The ticket ID to update

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

20 Aug 22 Aug