MCP.Market

Axcient x360Recover MCP server

by wyre-technology·io.github.wyre-technology/axcient-mcp·v1.0.1
No reviews yet

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

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Axcient x360Recover yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Axcient x360Recover tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 14 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Axcient x360Recover compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers

Install Axcient x360Recover in Claude Code, Cursor or VS Code

claude mcp add axcient-mcp -- docker run -i --rm ghcr.io/wyre-technology/axcient-mcp:v1.0.1
Add to Cursor

What the publisher says

From the Axcient x360Recover repository's README, as published. We do not edit it. Read it on GitHub

axcient-mcp

MCP server for Axcient x360Recover — BCDR clients, devices, backup jobs, vaults, and appliances. Built on @wyre-technology/node-axcient and the MCP v2 SDK, serving both the 2025-era initialize handshake and the 2026-07-28 stateless envelope from a single dual-era HTTP entrypoint.

Credentials

Generate an API key in the x360Portal: Settings → API Keys (see Axcient's key management guide).

request (AUTH_MODE=gateway); no server-side key is stored.

  • Local / stdio (Claude Desktop, CLI): set AXCIENTAPIKEY.
  • Hosted / gateway: the WYRE MCP Gateway injects the X-Axcient-Api-Key header per

Run locally (stdio)

npm install
npm run build
AXCIENT_API_KEY=your-key npm start

Run as HTTP (gateway / hosted)

MCP_TRANSPORT=http AUTH_MODE=env AXCIENT_API_KEY=your-key npm start
# → http://localhost:8080/mcp, health at http://localhost:8080/health

Docker

docker build --platform linux/amd64 --build-arg GITHUB_TOKEN=$(gh auth token) -t axcient-mcp .
docker run -p 8080:8080 -e AXCIENT_API_KEY=your-key axcient-mcp

Tools

20 tools, flat surface (no router — well under the fleet's ~25-tool threshold).

No destructive tools exist in this surface — the x360Recover public API (v0.3.1) has no delete/disable operations, so no confirmation/elicitation flow is wired up. See node-axcient's README for known API quirks (error-shape inconsistencies, list-endpoint schema documentation bugs) this server's error messages surface verbatim from the SDK.

License

Apache-2.0

Nothing above is checked by us. What we check is on the safety report.

Axcient x360Recover: common questions

Is Axcient x360Recover MCP server safe?
Mostly: it is graded B (75/100). Read the Axcient x360Recover safety report
How do I install Axcient x360Recover?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Axcient x360Recover need an API key?
Yes. The registry entry asks for AXCIENT_API_KEY.
Is Axcient x360Recover maintained?
The last commit was 16 days ago (2026-10-19). The latest release is v1.0.1.

More from wyre-technology →