Axcient x360Recover
OCI · GHCR.IO/WYRE-TECHNOLOGY/AXCIENT-MCP:V1.0.1
MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.
Available components
Last scanned (6 hours ago)
Scores higher than 67% 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 & Transparency6
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- 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 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 Management97
- Stability observed for 29 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 83 to 97. That category is still filling its 30-day observation window: 25 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.
- 6 Oct 26 −3
- Stability: pass → 0.83 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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/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 |
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 →
axcient_get_appliance ~61
Get a single appliance by ID, including model, storage, tunnel status, and health.
| Name | Type | Req | Description |
|---|---|---|---|
| appliance_id | number | yes | The Axcient appliance ID. |
| include_devices | boolean | – | Include 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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | 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). |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | The Axcient client ID (an x360Recover-managed customer/site, not the API caller). |
| vault_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | The Axcient client ID (an x360Recover-managed customer/site, not the API caller). |
| device_id | number | yes | The Axcient device (protected system) ID. |
| job_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | The Axcient client ID (an x360Recover-managed customer/site, not the API caller). |
| device_id | number | yes | The Axcient device (protected system) ID. |
| job_id | number | yes | 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. |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vault_id | number | yes | The 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).
| Name | Type | Req | Description |
|---|---|---|---|
| vault_id | number | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_devices | boolean | – | Include the device list in the response (default true). |
| service_id | string | – | 4-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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | 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). |
No output schema declared.
No examples provided.
axcient_list_clients ~41
List all clients (customer/site records) in the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| include_appliances | boolean | – | Include 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return. |
| offset | number | – | Pagination offset. |
No output schema declared.
No examples provided.
axcient_list_devices_by_client ~85
List devices belonging to a specific client.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | 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. |
No output schema declared.
No examples provided.
axcient_list_jobs_by_device ~65
List backup jobs configured for a device.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | number | yes | The Axcient client ID (an x360Recover-managed customer/site, not the API caller). |
| device_id | number | yes | The Axcient device (protected system) ID. |
No output schema declared.
No examples provided.
axcient_list_vaults ~92
List vaults (Private or Cloud) in the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| threshold_minutes | number | yes | Minutes without connectivity before the vault is marked WARNED. |
| vault_id | number | yes | The 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.
How do I install the Axcient x360Recover MCP server?
Axcient x360Recover runs locally as a container image, launched with docker run --rm -i -e AXCIENT_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL 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
claude mcp add wyre-technology-axcient-mcp -- docker run --rm -i -e AXCIENT_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/axcient-mcp:v1.0.1
This image reads AXCIENT_API_KEY, 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 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 47 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 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 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.