# SuperOps (oci · ghcr.io/wyre-technology/superops-mcp:v1.6.6)

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

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/superops-mcp:v1.6.6`: 41/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6.md), [page](https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/superops-mcp:v1.6.6`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1545 tokens (~70/item across 22 items; 21 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**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

### Claude

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

### Codex

```bash
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

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

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 41)

First indexed and scored.

## MCP tools (21)

### `superops_navigate` (~141 tokens)

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 parameters:

- `domain` (string, required): 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 -…

### `superops_status` (~16 tokens)

Show credentials status and available domains

### `superops_test_connection` (~22 tokens)

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

### `superops_clients_list` (~105 tokens)

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

Input parameters:

- `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

### `superops_clients_get` (~37 tokens)

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

Input parameters:

- `accountId` (string, required): The unique account ID of the client

### `superops_clients_search` (~59 tokens)

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

Input parameters:

- `max` (number): Maximum number of results (default: 20)
- `query` (string, required): Search term to find clients by name or email domain

### `superops_tickets_list` (~148 tokens)

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

Input parameters:

- `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

### `superops_tickets_get` (~34 tokens)

Get detailed information for a specific ticket by its ID.

Input parameters:

- `ticketId` (string, required): The unique ticket ID

### `superops_tickets_create` (~113 tokens)

Create a new ticket in SuperOps.ai.

Input parameters:

- `categoryName` (string): Service category name
- `clientId` (string, required): 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, required): Ticket subject/title
- `techGroupName` (string): Name of the technician group to assign

### `superops_tickets_update` (~122 tokens)

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

Input parameters:

- `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, required): The ticket ID to update

### `superops_tickets_add_note` (~69 tokens)

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

Input parameters:

- `content` (string, required): Note content
- `isPublic` (boolean): Whether the note is visible to the client (default: false)
- `ticketId` (string, required): The ticket ID

### `superops_tickets_log_time` (~92 tokens)

Log time spent on a ticket.

Input parameters:

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

### `superops_assets_list` (~115 tokens)

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

Input parameters:

- `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

### `superops_assets_get` (~38 tokens)

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

Input parameters:

- `assetId` (string, required): The unique asset ID

### `superops_assets_software` (~62 tokens)

Get the software inventory for a specific asset.

Input parameters:

- `assetId` (string, required): The unique asset ID
- `max` (number): Maximum number of results (default: 100)
- `search` (string): Search term to filter software by name

### `superops_assets_patches` (~71 tokens)

Get patch status and pending patches for a specific asset.

Input parameters:

- `assetId` (string, required): The unique asset ID
- `severity` (array): Filter by severity levels: Critical, Important, Moderate, Low
- `status` (string): Filter patches by status: Pending, Installed, or Failed

### `superops_technicians_list` (~93 tokens)

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

Input parameters:

- `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

### `superops_technicians_get` (~35 tokens)

Get detailed information for a specific technician by their ID.

Input parameters:

- `technicianId` (string, required): The unique technician ID

### `superops_technicians_groups` (~38 tokens)

List technician groups/teams in SuperOps.ai.

Input parameters:

- `max` (number): Maximum number of results (default: 50)

### `superops_custom_query` (~58 tokens)

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

Input parameters:

- `query` (string, required): The GraphQL query string
- `variables` (object): Variables to pass to the query

### `superops_custom_mutation` (~59 tokens)

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

Input parameters:

- `mutation` (string, required): The GraphQL mutation string
- `variables` (object): Variables to pass to the mutation

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6#diagnostics

## Score history

- 2026-08-22: 41
- 2026-08-21: 41
- 2026-08-20: 41

## Links

- Repository: https://github.com/wyre-technology/superops-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-superops-mcp/ghcr-io-wyre-technology-superops-mcp-v1-6-6