Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Axcient x360Recover

OCI · GHCR.IO/WYRE-TECHNOLOGY/AXCIENT-MCP:V1.0.1 · SCANNED AUG 22

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

38 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • 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.Unverified
  • Install-script risk not yet assessed.Unverified
  • 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.Unverified
Provenance & Transparency32
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1296 tokens (~64/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

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.

oci · ghcr.io/wyre-technology/axcient-mcp:v1.0.1

# add to Claude Code
claude mcp add wyre-technology-axcient-mcp -- docker run --rm -i ghcr.io/wyre-technology/axcient-mcp:v1.0.1
// .cursor/mcp.json
{
  "mcpServers": {
    "wyre-technology-axcient-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wyre-technology-axcient-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"
      ]
    }
  }
}
# add to Codex CLI
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/config.yaml
mcp_servers:
  wyre-technology-axcient-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wyre-technology-axcient-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "wyre-technology-axcient-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/axcient-mcp:v1.0.1"
      ]
    }
  }
}
Changelog

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.

  • 20 Aug 26 38

    First indexed and scored.

Diagnostics

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 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/axcient-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
MCP tools · 20 exposed · ~1,296 tokens

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.

Tool Tokens
axcient_get_appliance ~61

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

NameTypeReqDescription
appliance_idnumberyesThe Axcient appliance ID.
include_devicesbooleanInclude the device list in the response (default true).

No output schema declared.

No examples provided.

axcient_get_client ~72

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

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
include_appliancesbooleanInclude short appliance information in the response (default false).

No output schema declared.

No examples provided.

axcient_get_d2c_agent_token ~107

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.

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
vault_idnumberyesThe Axcient vault ID.

No output schema declared.

No examples provided.

axcient_get_device ~50

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

NameTypeReqDescription
device_idnumberyesThe Axcient device (protected system) ID.

No output schema declared.

No examples provided.

axcient_get_device_autoverify ~50

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

NameTypeReqDescription
device_idnumberyesThe Axcient device (protected system) ID.

No output schema declared.

No examples provided.

axcient_get_device_restore_points ~47

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

NameTypeReqDescription
device_idnumberyesThe Axcient device (protected system) ID.

No output schema declared.

No examples provided.

axcient_get_job ~84

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

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
device_idnumberyesThe Axcient device (protected system) ID.
job_idnumberyesThe Axcient backup job ID.

No output schema declared.

No examples provided.

axcient_get_job_history ~155

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.

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
device_idnumberyesThe Axcient device (protected system) ID.
job_idnumberyesThe Axcient backup job ID.
limitnumberMax results to return.
offsetnumberPagination offset.
start_time_beginnumberUnix timestamp — only return history entries starting at/after this time.

No output schema declared.

No examples provided.

axcient_get_organization ~22

Get the organization associated with the authenticating API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

axcient_get_vault ~39

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

NameTypeReqDescription
vault_idnumberyesThe Axcient vault ID.

No output schema declared.

No examples provided.

axcient_get_vault_threshold ~43

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

NameTypeReqDescription
vault_idnumberyesThe Axcient vault ID.

No output schema declared.

No examples provided.

axcient_list_appliances ~64

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

NameTypeReqDescription
include_devicesbooleanInclude the device list in the response (default true).
service_idstring4-character appliance service SID to filter by.

No output schema declared.

No examples provided.

axcient_list_appliances_by_client ~66

List appliances belonging to a specific client.

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
include_devicesbooleanInclude the device list in the response (default true).

No output schema declared.

No examples provided.

axcient_list_clients ~41

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

NameTypeReqDescription
include_appliancesbooleanInclude short appliance information in the response (default false).

No output schema declared.

No examples provided.

axcient_list_devices ~47

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

NameTypeReqDescription
limitnumberMax results to return.
offsetnumberPagination offset.

No output schema declared.

No examples provided.

axcient_list_devices_by_client ~85

List devices belonging to a specific client.

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
d2c_onlybooleanReturn only D2C (direct-to-cloud) devices.
service_idstring4-character appliance/service SID to filter by.

No output schema declared.

No examples provided.

axcient_list_jobs_by_device ~65

List backup jobs configured for a device.

NameTypeReqDescription
client_idnumberyesThe Axcient client ID (an x360Recover-managed customer/site, not the API caller).
device_idnumberyesThe Axcient device (protected system) ID.

No output schema declared.

No examples provided.

axcient_list_vaults ~92

List vaults (Private or Cloud) in the organization.

NameTypeReqDescription
activebooleanFilter by active state.
include_devicesbooleanInclude the device list in the response (default true).
limitnumberMax results to return.
vault_typestringFilter by vault type.
with_urlbooleanFilter to vaults that have a URL.

No output schema declared.

No examples provided.

axcient_set_vault_threshold ~81

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.

NameTypeReqDescription
threshold_minutesnumberyesMinutes without connectivity before the vault is marked WARNED.
vault_idnumberyesThe Axcient vault ID.

No output schema declared.

No examples provided.

axcient_test_connection ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.