jorgedlcruz/modelcontextprotocol_veeam

MCPcommunity
jorgedlcruzMITUpdated 9mo agoGitHub

A Repository with a collection of MCP Servers for Veeam

Democratizing AI access to Veeam's powerful data protection ecosystem The Model Context Protocol for Veeam project aims to bridge the gap between artificial intelligence and Veeam's robust data protection ecosystem. By leveraging the Model Context Protocol (MCP), I am enabling AI assistants to directly interact with Veeam's feature-rich APIs, creating new possibilities for data management,…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
10GitHub stars
3Forks
9mo agoLast update
Package
Authorjorgedlcruz
LicenseMIT
Sourcegithub
GitHubjorgedlcruz/modelcontextprotocol_veeam
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface13 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

auth-vbrNo description published

This tool published no description. Forge does not invent one.

get-backup-objectsNo description published

This tool published no description. Forge does not invent one.

get-proxiesNo description published

This tool published no description. Forge does not invent one.

get-repositoriesNo description published

This tool published no description. Forge does not invent one.

get-backup-sessionsNo description published

This tool published no description. Forge does not invent one.

get-config-backupNo description published

This tool published no description. Forge does not invent one.

start-config-backupNo description published

This tool published no description. Forge does not invent one.

get-license-infoNo description published

This tool published no description. Forge does not invent one.

get-license-workloadsNo description published

This tool published no description. Forge does not invent one.

get-malware-eventsNo description published

This tool published no description. Forge does not invent one.

get-protection-groupsNo description published

This tool published no description. Forge does not invent one.

get-restore-pointsNo description published

This tool published no description. Forge does not invent one.

get-server-infoNo description published

This tool published no description. Forge does not invent one.

0 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Democratizing AI access to Veeam's powerful data protection ecosystem The Model Context Protocol for Veeam project aims to bridge the gap between artificial intelligence and Veeam's robust data protection ecosystem. By leveraging the Model Context Protocol (MCP), I am enabling AI assistants to directly interact with Veeam's feature-rich APIs, creating new possibilities for data management, monitoring, and protection. My goal is to democratize access to Veeam's powerful capabilities through…

Alternatives
Comparing tool surfaces…

Tools exposed

13 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.