MSP360
OCI · GHCR.IO/WYRE-AI/MSP360-MCP
MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.
Available components
Last scanned (1 hour ago)
Scores higher than 50% of OCI servers
Category Monitoring and Observability
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 & Transparency32
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 622 tokens (~44/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
- 23 Oct 26 +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.
- 22 Oct 26 38
First indexed and scored.
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 23 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/msp360-mcp@v1.0.1
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 →
msp360_get_company ~31
Get a single MSP360 company by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Company ID (GUID). |
No output schema declared.
No examples provided.
msp360_get_computer ~32
Get a single managed computer by its HID.
| Name | Type | Req | Description |
|---|---|---|---|
| hid | string | yes | HID of the computer. |
No output schema declared.
No examples provided.
msp360_get_license ~30
Get a single MSP360 license by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | License unique identifier. |
No output schema declared.
No examples provided.
msp360_get_monitoring ~31
Get status data for the latest backup plan runs on all endpoints (account-wide health/alerts).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
msp360_get_monitoring_for_user ~44
Get status data for the latest backup plan runs on online endpoints, filtered to a specific user.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | Existing user ID. |
No output schema declared.
No examples provided.
msp360_get_plan ~47
Get a single backup/restore plan on a computer by plan ID.
| Name | Type | Req | Description |
|---|---|---|---|
| hid | string | yes | HID of the computer. |
| id | string | yes | Plan ID (GUID). |
No output schema declared.
No examples provided.
msp360_get_plan_history ~95
Get run history for a backup/restore plan on a computer, optionally filtered to a specific date.
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | – | Filter day (1-31). |
| hid | string | yes | HID of the computer. |
| id | string | yes | Plan ID (GUID). |
| month | number | – | Filter month (1-12). |
| year | number | – | Filter year (2023-9999). |
No output schema declared.
No examples provided.
msp360_get_plan_info ~47
Get status/info for a backup/restore plan on a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| hid | string | yes | HID of the computer. |
| id | string | yes | Plan ID (GUID). |
No output schema declared.
No examples provided.
msp360_list_companies ~27
List all companies (customer organizations) managed under this MSP360 provider account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
msp360_list_computers ~52
List managed computers (endpoints), paginated by offset/count.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of computers to retrieve. |
| offset | number | yes | Number of computers to skip before retrieving. |
No output schema declared.
No examples provided.
msp360_list_licenses ~39
List available MSP360 licenses, optionally filtered to only unassigned ones.
| Name | Type | Req | Description |
|---|---|---|---|
| isAvailable | boolean | – | Only return unassigned licenses. |
No output schema declared.
No examples provided.
msp360_list_plans ~33
List backup/restore plans configured on a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| hid | string | yes | HID of the computer. |
No output schema declared.
No examples provided.
msp360_start_plan ~58
Start a backup run for a plan on a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| hid | string | yes | HID of the computer. |
| id | string | yes | Plan ID (GUID). |
| mode | string | – | Vendor-defined run mode, if applicable. |
No output schema declared.
No examples provided.
msp360_stop_plan ~56
Stop a currently running backup for a plan on a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force-stop the run. |
| hid | string | yes | HID of the computer. |
| id | string | yes | Plan ID (GUID). |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/msp360-mcp
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.
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.