TractorBeeam365 MCP
OCI · GHCR.IO/RINGOSYSTEMS/TRACTORBEEAM-MCP:2.2.0 · SCANNED SEP 20
MCP server for Veeam Backup for Microsoft 365: read-only review + gated, audited restore tier.
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 917 tokens (~48/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
How do I install the TractorBeeam365 MCP server?
TractorBeeam365 MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0. 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/ringosystems/tractorbeeam-mcp:2.2.0
claude mcp add ringosystems-tractorbeeam-mcp -- docker run --rm -i ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0
{
"mcpServers": {
"ringosystems-tractorbeeam-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"
]
}
}
} {
"servers": {
"ringosystems-tractorbeeam-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"
]
}
}
} codex mcp add ringosystems-tractorbeeam-mcp -- docker run --rm -i ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ringosystems-tractorbeeam-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"
],
"enabled": true
}
}
} mcp_servers:
ringosystems-tractorbeeam-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"] {
"McpServers": {
"ringosystems-tractorbeeam-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"
]
}
}
} {
"mcpServers": {
"ringosystems-tractorbeeam-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0"
]
}
}
} 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.
- 20 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 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.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 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.
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 20 Sept 2026 · Analysed oci/ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0
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 →
cloud_lock_audit ~72
Cross-check cloud immutability at the SOURCE: queries each Backblaze B2 / S3 bucket VB365 uses (Object Lock mode, retention window, versioning) and flags any mismatch vs what VB365 reports. Needs B2_*/S3_* creds; read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gap_coverage_summary ~56
Backup COVERAGE % per workload by comparing LIVE Microsoft 365 (Graph) against what VB365 actually protects. Reveals licensed users/sites/teams that are NOT backed up. Read-only; needs GRAPH_* creds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gap_unprotected_objects ~54
List LIVE Microsoft 365 objects that are NOT protected by any VB365 job. workload = mailbox | onedrive | sharepoint | teams. Read-only; needs GRAPH_*.
| Name | Type | Req | Description |
|---|---|---|---|
| workload | string | – | – |
No output schema declared.
No examples provided.
vb365_api_root ~42
List the available VB365 REST resources + version (GET /<version>/). Good first call to confirm connectivity and discover endpoint names for this VB365 version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vb365_get ~71
Read-only GET against ANY VB365 REST resource under the API version base. Examples: path='Jobs', path='Organizations/<id>/Users'. GET only — cannot modify anything. Use vb365_api_root if unsure of resource names.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
vb365_get_job ~37
Full details for one backup job (schedule policy, scope, repository, last/next run).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
vb365_get_object_storage ~34
Full configuration for one object storage / cloud repository by id. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_id | string | yes | – |
No output schema declared.
No examples provided.
vb365_health_summary ~79
One-shot READ-ONLY config/health review: organizations, jobs + last status, repositories (capacity / retention / immutability), cloud storage, proxies, license, trend anomalies, plus a 'flags' list of likely concerns. Every section is fetched read-only and isolated, so a partial failure still returns the rest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vb365_job_scope ~50
The selected + excluded items of a backup job (which users/groups/sites/teams it protects, and per-user mailbox/OneDrive/site facets). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
vb365_license ~19
License information (edition, licensed users, expiry).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vb365_list_job_sessions ~41
Recent job sessions / run results. Optionally filter to one job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
vb365_list_jobs ~28
List backup jobs, including schedule policy and last status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
vb365_list_object_storage ~74
List object storage (cloud) repositories — Amazon S3, S3 Compatible (e.g. Backblaze B2), Azure Blob, Wasabi, IBM Cloud, Glacier. Queries the dedicated ObjectStorageRepositories resource AND object-storage-backed backup repos (v8).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
vb365_list_organizations ~30
List the backed-up Microsoft 365 organizations (tenants).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
vb365_list_proxies ~18
List backup proxies and their status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vb365_list_repositories ~26
List backup repositories (capacity, free space, retention, immutability).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vb365_list_restore_points ~52
List backup restore points (snapshots): time, job/org, workloads present, immutability-expiry, copy/archive flags. Read-only — feeds restore + trends.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
vb365_org_inventory ~47
VB365's view of an organization's objects. kind = users | groups | sites | teams. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
vb365_trends ~87
Read-only trend & anomaly analysis over job-session history: per-job success/failure drift (a job that 'succeeded' today but fails often), repo capacity-full projection, restore-test cadence per org, and RPO compliance. Surfaces issues a single latest-status check misses.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| rpo_hours | number | – | – |
No output schema declared.
No examples provided.
What is the TractorBeeam365 MCP server?
TractorBeeam365 MCP is listed in the public MCP registry as io.github.Ringosystems/tractorbeeam-mcp. MCP server for Veeam Backup for Microsoft 365: read-only review + gated, audited restore tier. This page covers its container image (ghcr.io/ringosystems/tractorbeeam-mcp:2.2.0).
Is the TractorBeeam365 MCP server safe to use?
TractorBeeam365 MCP scores 51 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 TractorBeeam365 MCP server expose?
TractorBeeam365 MCP exposes 19 tools: vb365_api_root, vb365_list_organizations, vb365_list_jobs, vb365_get_job, vb365_job_scope, and 14 more. Their descriptions and schemas cost roughly 917 tokens of context every time the server is loaded.
Is the TractorBeeam365 MCP server still maintained?
TractorBeeam365 MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 TractorBeeam365 MCP server under?
TractorBeeam365 MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.