SuperOps
OCI · GHCR.IO/WYRE-TECHNOLOGY/SUPEROPS-MCP:V1.6.6
MCP server for SuperOps unified PSA+RMM — clients, tickets, assets, and more.
Available components
Last scanned (3 hours ago)
Scores higher than 82% of OCI servers
Category CRM and Sales
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 → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 57 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 10 Oct 26 +1
- Stability: 0.90 → pass security
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 80 to 90. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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 17 Oct 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 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
superops_assets_get ~38
Get detailed information for a specific asset including hardware, OS, and network details.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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 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.
| 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.
| 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.
| 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 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).
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
How do I install the SuperOps MCP server?
SuperOps runs locally as a container image, launched with docker run --rm -i -e SUPEROPS_API_TOKEN -e SUPEROPS_SUBDOMAIN -e SUPEROPS_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/superops-mcp:v1.6.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-technology/superops-mcp:v1.6.6
claude mcp add wyre-technology-superops-mcp -- docker run --rm -i -e SUPEROPS_API_TOKEN -e SUPEROPS_SUBDOMAIN -e SUPEROPS_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/superops-mcp:v1.6.6
This image reads SUPEROPS_API_TOKEN, SUPEROPS_SUBDOMAIN, SUPEROPS_REGION, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the SuperOps MCP server?
SuperOps is an MCP server listed in the public MCP registry as io.github.wyre-technology/superops-mcp. MCP server for SuperOps unified PSA+RMM, clients, tickets, assets, and more. This page covers its container image (ghcr.io/wyre-technology/superops-mcp:v1.6.6).
Is the SuperOps MCP server safe to use?
SuperOps scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SuperOps MCP server expose?
SuperOps exposes 21 tools: superops_navigate, superops_status, superops_test_connection, superops_clients_list, superops_clients_get, and 16 more. Their descriptions and schemas cost roughly 1,527 tokens of context every time the server is loaded.
Is the SuperOps MCP server still maintained?
SuperOps is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SuperOps MCP server under?
SuperOps declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.