# MSP360 (oci · ghcr.io/wyre-ai/msp360-mcp)

MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- oci · `ghcr.io/wyre-ai/msp360-mcp`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-msp360-mcp/ghcr-io-wyre-ai-msp360-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-msp360-mcp/ghcr-io-wyre-ai-msp360-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/msp360-mcp`
- Version: `v1.0.1`
- 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-10-23.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 622 tokens (~44/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### How do I install the MSP360 MCP server?

MSP360 runs locally as a container image, launched with docker run --rm -i -e MSP360_USERNAME -e MSP360_PASSWORD -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/msp360-mcp:v1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-msp360-mcp -- docker run --rm -i -e MSP360_USERNAME -e MSP360_PASSWORD -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/msp360-mcp:v1.0.1
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-msp360-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MSP360_USERNAME",
        "-e",
        "MSP360_PASSWORD",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### VS Code

```json
{
  "servers": {
    "wyre-ai-msp360-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MSP360_USERNAME",
        "-e",
        "MSP360_PASSWORD",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### Codex

```bash
codex mcp add wyre-ai-msp360-mcp -- docker run --rm -i -e MSP360_USERNAME -e MSP360_PASSWORD -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/msp360-mcp:v1.0.1
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-msp360-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "MSP360_USERNAME",
        "-e",
        "MSP360_PASSWORD",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### Hermes

```yaml
mcp_servers:
  wyre-ai-msp360-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "MSP360_USERNAME", "-e", "MSP360_PASSWORD", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"]
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-msp360-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MSP360_USERNAME",
        "-e",
        "MSP360_PASSWORD",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-msp360-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MSP360_USERNAME",
        "-e",
        "MSP360_PASSWORD",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads MSP360_USERNAME, MSP360_PASSWORD, 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.

## 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-10-23 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 38)

First indexed and scored.

## MCP tools (14)

### `msp360_list_companies` (~27 tokens)

List all companies (customer organizations) managed under this MSP360 provider account.

### `msp360_get_company` (~31 tokens)

Get a single MSP360 company by ID.

Input parameters:

- `id` (string, required): Company ID (GUID).

### `msp360_list_computers` (~52 tokens)

List managed computers (endpoints), paginated by offset/count.

Input parameters:

- `count` (number, required): Number of computers to retrieve.
- `offset` (number, required): Number of computers to skip before retrieving.

### `msp360_get_computer` (~32 tokens)

Get a single managed computer by its HID.

Input parameters:

- `hid` (string, required): HID of the computer.

### `msp360_list_plans` (~33 tokens)

List backup/restore plans configured on a computer.

Input parameters:

- `hid` (string, required): HID of the computer.

### `msp360_get_plan` (~47 tokens)

Get a single backup/restore plan on a computer by plan ID.

Input parameters:

- `hid` (string, required): HID of the computer.
- `id` (string, required): Plan ID (GUID).

### `msp360_get_plan_info` (~47 tokens)

Get status/info for a backup/restore plan on a computer.

Input parameters:

- `hid` (string, required): HID of the computer.
- `id` (string, required): Plan ID (GUID).

### `msp360_get_plan_history` (~95 tokens)

Get run history for a backup/restore plan on a computer, optionally filtered to a specific date.

Input parameters:

- `day` (number): Filter day (1-31).
- `hid` (string, required): HID of the computer.
- `id` (string, required): Plan ID (GUID).
- `month` (number): Filter month (1-12).
- `year` (number): Filter year (2023-9999).

### `msp360_start_plan` (~58 tokens)

Start a backup run for a plan on a computer.

Input parameters:

- `hid` (string, required): HID of the computer.
- `id` (string, required): Plan ID (GUID).
- `mode` (string): Vendor-defined run mode, if applicable.

### `msp360_stop_plan` (~56 tokens)

Stop a currently running backup for a plan on a computer.

Input parameters:

- `force` (boolean): Force-stop the run.
- `hid` (string, required): HID of the computer.
- `id` (string, required): Plan ID (GUID).

### `msp360_get_monitoring` (~31 tokens)

Get status data for the latest backup plan runs on all endpoints (account-wide health/alerts).

### `msp360_get_monitoring_for_user` (~44 tokens)

Get status data for the latest backup plan runs on online endpoints, filtered to a specific user.

Input parameters:

- `userId` (string, required): Existing user ID.

### `msp360_list_licenses` (~39 tokens)

List available MSP360 licenses, optionally filtered to only unassigned ones.

Input parameters:

- `isAvailable` (boolean): Only return unassigned licenses.

### `msp360_get_license` (~30 tokens)

Get a single MSP360 license by ID.

Input parameters:

- `id` (string, required): License unique identifier.

## Diagnostics

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

## Score history

- 2026-10-23: 39
- 2026-10-22: 38

## Common questions

### What is the MSP360 MCP server?

MSP360 is an MCP server listed in the public MCP registry as io.github.WYRE-AI/msp360-mcp. MCP server for MSP360's Managed Backup Service API, companies, computers, and backup plans. This page covers its container image (ghcr.io/wyre-ai/msp360-mcp).

### Is the MSP360 MCP server safe to use?

MSP360 scores 39 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 MSP360 MCP server expose?

MSP360 exposes 14 tools: msp360_list_companies, msp360_get_company, msp360_list_computers, msp360_get_computer, msp360_list_plans, and 9 more. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.

### Is the MSP360 MCP server still maintained?

MSP360 is still listed as active in the MCP registry. We last reached this channel on 23 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 MSP360 MCP server under?

MSP360 declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/msp360-mcp
- Repository: https://github.com/WYRE-AI/msp360-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-msp360-mcp/ghcr-io-wyre-ai-msp360-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-msp360-mcp/ghcr-io-wyre-ai-msp360-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-msp360-mcp/ghcr-io-wyre-ai-msp360-mcp