Axcient x360Recover MCP server and AI skills

What it can do

• Clients & coverage contextIdentify the connected partner and follow each client's protected devices and appliances before assessing coverage.5skills
  • Identify the partner organization whose backup fleet this connection reads.
  • See the backup clients and their protected-device counters to establish the scope of a review.
  • Check a client's active status and protection counters before investigating its devices.
  • Inspect the protected devices belonging to a client, including their jobs and latest verification details.
  • Find the backup appliances assigned to a client to investigate its local protection infrastructure.
• Devices & recovery evidenceFind devices needing attention, inspect available recovery points, and examine the verification evidence already recorded.4skills

  Evidence describes recorded results; it does not start a restore or a verification run.

  • Find protected devices by client, health, protection type or device type, with their latest restore-point and verification status.
  • Investigate a device's full backup record, including jobs, volumes, usage and latest verification details.
  • Inspect a device's available recovery points and their state to understand what recovery data is recorded.
  • Review a device's recorded boot-verification checks and available screenshot evidence.
• Backup jobs & execution historyInspect configured jobs and their returned execution history to understand failures, timing and recovery-point progress.4skills

  A history summary covers the returned runs and requested window, not an assumed complete lifetime history.

  • Inspect a device's configured backup jobs, including their schedules and replication links, before following a failure.
  • Examine a particular backup job's configuration, including its health and latest recovery points.
  • Read a backup job's execution outcomes over a selected history window, including timestamps and failure messages.
  • Summarize returned job runs into completion and failure counts, success rate, average duration and recent errors.
• Appliances & vault healthReview local backup infrastructure and replication targets, including their reported health and connectivity settings.5skills

  Reads existing configuration and reported health. Capacity is only reported where the source supplies it.

  • Find appliances needing attention, including their reported health, software version and last tunnel contact.
  • Inspect an appliance's detailed record to investigate its condition and protected devices.
  • Review the available replication targets and the device and usage information they report.
  • Inspect a particular replication target's record to investigate its reported condition.
  • Read how long a vault may lose contact before its connectivity status becomes a warning.
• Backup health & coverage gapsPrioritize unhealthy or stale devices and compare recorded endpoint links with an available RMM roster.3skills

  An unmatched endpoint is unresolved until its mapping is checked. The comparison requires a separately available Asio RMM roster.

  • Compare backup health across clients and identify the devices contributing to each client's concerns.
  • Find devices with a missing restore point or one older than the requested age threshold.
  • Compare supplied RMM endpoint identifiers with recorded backup-device links and surface unmatched endpoints for coverage review.

How it has been taught to work it

Playbooks are the vetted techniques a session loads for this platform — what to check, in what order, and what a number means before it is reported.

• Axcient ↔ Asio — RMM-managed endpoints with no backupWhich of our RMM-managed endpoints have no backup — backup coverage gaps, unprotected endpoints, "is this managed machine actually protected", per-client or fleet-wide coverage reconciliation.
  Vetted Aug 14, 2026
• Axcient x360Recover domain model (BCDR, not an RMM)Always when Axcient is attached. Its domain model — appliance vs D2C, restore points, jobs, AutoVerify, health statuses, the Asio join — and why it is not an RMM.
  Vetted Aug 31, 2026Always on
• Backup health review — fleet-wide, with AutoVerify evidenceFleet-wide backup health review, "is everything backing up okay", health/status check across all clients, weekly or monthly backup review, QBR-shaped backup health section.
  Vetted Aug 13, 2026
• Job history drill-down — per-run evidence beyond the latest restore point"Why does this backup job keep failing", "show me this job's run history / success rate", a device-level offender from the health summary or the stale-backups check that needs per-job forensic evidence, or any question about a specific job's reliability over time rather than its latest snapshot.
  Vetted Sep 2, 2026
• Querying Axcient — rollups first, trimmed summaries, and pre-authed screenshotsAlways when Axcient is attached. Why fleet questions start with the rollups, which scope each kind of read needs, and the screenshot-link rule.
  Vetted Aug 31, 2026Always on

Plus 18 more every session carries regardless of platform — how to shape an investigation, keep every number traceable, and say plainly when something is broken.