# Axcient x360Recover (oci · ghcr.io/wyre-technology/axcient-mcp:v1.0.1)

MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.

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

## Components

- oci · `ghcr.io/wyre-technology/axcient-mcp:v1.0.1`: 38/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-axcient-mcp/ghcr-io-wyre-technology-axcient-mcp-v1-0-1.md), [page](https://verifymcp.io/servers/wyre-technology-axcient-mcp/ghcr-io-wyre-technology-axcient-mcp-v1-0-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/axcient-mcp: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-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**: 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 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1296 tokens (~64/item across 20 items; 20 tools + 0 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 current MCP spec version (2026-07-28).

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

### How do I install the Axcient x360Recover MCP server?

Axcient x360Recover runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/axcient-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-technology-axcient-mcp -- docker run --rm -i ghcr.io/wyre-technology/axcient-mcp:v1.0.1
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add wyre-technology-axcient-mcp -- docker run --rm -i ghcr.io/wyre-technology/axcient-mcp:v1.0.1
```

### opencode

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "wyre-technology-axcient-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"
      ]
    }
  }
}
```

### Other

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

## 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 38)

First indexed and scored.

## MCP tools (20)

### `axcient_test_connection` (~25 tokens)

Verify the configured Axcient API key works by fetching the organization record.

### `axcient_get_organization` (~22 tokens)

Get the organization associated with the authenticating API key.

### `axcient_list_clients` (~41 tokens)

List all clients (customer/site records) in the organization.

Input parameters:

- `include_appliances` (boolean): Include short appliance information in the response (default false).

### `axcient_get_client` (~72 tokens)

Get a single client by ID, including its health status and protected-system counts.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `include_appliances` (boolean): Include short appliance information in the response (default false).

### `axcient_get_d2c_agent_token` (~107 tokens)

Mint a D2C (direct-to-cloud) agent enrollment token for a client/vault pair, used to install the D2C backup agent on a new protected system. Each call mints a new token; it does not affect existing devices or data.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `vault_id` (number, required): The Axcient vault ID.

### `axcient_list_devices` (~47 tokens)

List all devices (protected systems) across the organization. Supports limit/offset pagination.

Input parameters:

- `limit` (number): Max results to return.
- `offset` (number): Pagination offset.

### `axcient_list_devices_by_client` (~85 tokens)

List devices belonging to a specific client.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `d2c_only` (boolean): Return only D2C (direct-to-cloud) devices.
- `service_id` (string): 4-character appliance/service SID to filter by.

### `axcient_get_device` (~50 tokens)

Get full detail for a single device, including OS, health status, thresholds, jobs, and vaults.

Input parameters:

- `device_id` (number, required): The Axcient device (protected system) ID.

### `axcient_get_device_autoverify` (~50 tokens)

Get AutoVerify (automated screenshot boot verification) results for a device, grouped by vault.

Input parameters:

- `device_id` (number, required): The Axcient device (protected system) ID.

### `axcient_get_device_restore_points` (~47 tokens)

Get available restore points for a device, grouped by the cloud vault they replicate to.

Input parameters:

- `device_id` (number, required): The Axcient device (protected system) ID.

### `axcient_list_jobs_by_device` (~65 tokens)

List backup jobs configured for a device.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `device_id` (number, required): The Axcient device (protected system) ID.

### `axcient_get_job` (~84 tokens)

Get a single backup job by ID, including thresholds and health status.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `device_id` (number, required): The Axcient device (protected system) ID.
- `job_id` (number, required): The Axcient backup job ID.

### `axcient_get_job_history` (~155 tokens)

Get run history for a backup job. Known API quirk: this endpoint is occasionally nonfunctional in production (community-reported); treat failures here as an Axcient-side issue, not a client bug.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `device_id` (number, required): The Axcient device (protected system) ID.
- `job_id` (number, required): The Axcient backup job ID.
- `limit` (number): Max results to return.
- `offset` (number): Pagination offset.
- `start_time_begin` (number): Unix timestamp — only return history entries starting at/after this time.

### `axcient_list_vaults` (~92 tokens)

List vaults (Private or Cloud) in the organization.

Input parameters:

- `active` (boolean): Filter by active state.
- `include_devices` (boolean): Include the device list in the response (default true).
- `limit` (number): Max results to return.
- `vault_type` (string): Filter by vault type.
- `with_url` (boolean): Filter to vaults that have a URL.

### `axcient_get_vault` (~39 tokens)

Get a single vault by ID, including storage usage and assigned devices.

Input parameters:

- `vault_id` (number, required): The Axcient vault ID.

### `axcient_get_vault_threshold` (~43 tokens)

Get a vault's connectivity threshold (minutes before it's marked WARNED for lost connectivity).

Input parameters:

- `vault_id` (number, required): The Axcient vault ID.

### `axcient_set_vault_threshold` (~81 tokens)

Set a vault's connectivity threshold in minutes. This changes alerting behavior only — it does not affect backups, replication, or stored data, and can be changed again at any time.

Input parameters:

- `threshold_minutes` (number, required): Minutes without connectivity before the vault is marked WARNED.
- `vault_id` (number, required): The Axcient vault ID.

### `axcient_list_appliances` (~64 tokens)

List appliances (BRC/x360Recover physical or virtual backup servers) in the organization.

Input parameters:

- `include_devices` (boolean): Include the device list in the response (default true).
- `service_id` (string): 4-character appliance service SID to filter by.

### `axcient_list_appliances_by_client` (~66 tokens)

List appliances belonging to a specific client.

Input parameters:

- `client_id` (number, required): The Axcient client ID (an x360Recover-managed customer/site, not the API caller).
- `include_devices` (boolean): Include the device list in the response (default true).

### `axcient_get_appliance` (~61 tokens)

Get a single appliance by ID, including model, storage, tunnel status, and health.

Input parameters:

- `appliance_id` (number, required): The Axcient appliance ID.
- `include_devices` (boolean): Include the device list in the response (default true).

## Diagnostics

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

## Score history

- 2026-08-22: 38
- 2026-08-21: 38
- 2026-08-20: 38

## Common questions

### What is the Axcient x360Recover MCP server?

Axcient x360Recover is an MCP server listed in the public MCP registry as io.github.wyre-technology/axcient-mcp. MCP server for Axcient x360Recover, BCDR clients, devices, jobs, vaults, and appliances. This page covers its container image (ghcr.io/wyre-technology/axcient-mcp:v1.0.1).

### Is the Axcient x360Recover MCP server safe to use?

Axcient x360Recover scores 38 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 Axcient x360Recover MCP server expose?

Axcient x360Recover exposes 20 tools: axcient_test_connection, axcient_get_organization, axcient_list_clients, axcient_get_client, axcient_get_d2c_agent_token, and 15 more. Their descriptions and schemas cost roughly 1,296 tokens of context every time the server is loaded.

### Is the Axcient x360Recover MCP server still maintained?

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

Axcient x360Recover 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

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