TractorBeeam365 MCP vs Axcient x360Recover
TractorBeeam365 MCP is an MCP server published by Ringosystems. Marketplaces we read that list it: 1 (Official MCP Registry). Axcient x360Recover is an MCP server published by wyre-technology. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  TractorBeeam365 MCP |  Axcient x360Recover |
|---|---|---|
| Official MCP Registry | Listed Version: 2.2.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | TractorBeeam365 MCP | Axcient x360Recover |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0) | On your machine (ghcr.io/wyre-technology/axcient-mcp:v1.0.1) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ringosystems/tractorbeeam-mcp | github.com/wyre-technology/axcient-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
TractorBeeam365 MCP
MCP server for Veeam Backup for Microsoft 365: read-only review + gated, audited restore tier.
Axcient x360Recover
MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.
How to run each
TractorBeeam365 MCP As a local MCP server: Docker image
claude mcp add --env "VB365_HOST=<YOUR_VB365_HOST>" --env "VB365_PASSWORD=<YOUR_VB365_PASSWORD>" --env "VB365_USERNAME=<YOUR_VB365_USERNAME>" --transport stdio tractorbeeam-mcp -- docker run -i --rm -e VB365_HOST -e VB365_PASSWORD -e VB365_USERNAME ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0Requires: VB365_HOST, VB365_PASSWORD (secret), VB365_USERNAME (secret)
Axcient x360Recover As a local MCP server: Docker image
claude mcp add --env "AXCIENT_API_KEY=<YOUR_AXCIENT_API_KEY>" --transport stdio axcient-mcp -- docker run -i --rm -e AXCIENT_API_KEY ghcr.io/wyre-technology/axcient-mcp:v1.0.1Requires: AXCIENT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only TractorBeeam365 MCP asks for
VB365_HOSTVB365_PASSWORD (secret)VB365_USERNAME (secret)
Only Axcient x360Recover asks for
AUTH_MODEAXCIENT_API_KEY (secret)LOG_LEVELMCP_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: TractorBeeam365 MCP · What it can do: Axcient x360Recover · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.