
Axcient x360Recover
io.github.WYRE-AI由 GitHub 账号 WYRE-AI 发布v1.0.5更新于 Nov 21, 2026
MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.
概览
面向 Axcient x360Recover 的 MCP 服务器,让助手查看 BCDR 客户、设备、备份任务、保管库与一体机。
- 可以做什么
- 验证 API 密钥并读取其所属组织
- 列出并获取客户(客户/站点记录)与设备,含按客户列设备
- 查看 AutoVerify 结果与设备恢复点
- 列出备份任务,并获取任务详情与按设备的历史记录
- 列出保管库与一体机,读取或设置保管库连通性阈值
- 签发 D2C 代理注册令牌
- 适用场景
- 适合让助手回答托管备份与灾难恢复环境的问题:有哪些客户与设备、备份任务和 AutoVerify 检查是否正常、有哪些可用恢复点,无需手动打开 x360Portal。
- 运行要求
- 以 stdio 本地进程运行(从源码构建的 Node.js 项目,或已发布的容器镜像)。stdio 或 AUTH_MODE=env 时需要 AXCIENT_API_KEY 中的 x360Portal API 密钥。HTTP 托管还需 CONDUIT_S2S_SECRET,网关模式下每个请求需带 X-Axcient-Api-Key 请求头。需要访问 Axcient API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Axcient x360Recover,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
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).
Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file.
- Local / stdio (Claude Desktop, CLI): set
AXCIENT_API_KEY. The stdio transport does not useCONDUIT_S2S_SECRET. - Hosted / gateway: the WYRE MCP Gateway injects
X-Axcient-Api-Keyper request (AUTH_MODE=gateway). The gateway compose service does not setAXCIENT_API_KEYand does not useenv_file.
/health and /healthz stay unauthenticated and do not read credentials.
X-Gateway-S2S signing
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S:
v1 is HMAC-SHA256 over the ASCII message t=<unix seconds>, keyed with CONDUIT_S2S_SECRET, hex-encoded. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never logged.
In AUTH_MODE=gateway, /mcp also requires X-Axcient-Api-Key. A request missing that header returns 401 and does not fall back to AXCIENT_API_KEY.
Run locally (stdio)
Run as HTTP (gateway / hosted)
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning:
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, the Axcient API key arrives on each request as X-Axcient-Api-Key; it is not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset, runs AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject AXCIENT_API_KEY:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses AXCIENT_API_KEY:
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
来源:README.md,提交 48bdd1d
工具
0版本历史
3- v1.0.5最新Nov 21, 2026
- v1.0.4Oct 14, 2026
- v1.0.3Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。