Veeam VSPC MCP vs InnoVint MCP by usefulapi
Veeam VSPC MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). InnoVint MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |   Veeam VSPC MCP |   InnoVint MCP by usefulapi |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.9 Forks (GitHub): 17 Stars (GitHub): 73 Not marked · First seen |
Listed Version: 1.7.5 Forks (GitHub): 0 Stars (GitHub): 1 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 | Veeam VSPC MCP | InnoVint MCP by usefulapi |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 73 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 17 (better) | 0 (worse) |
| Last release (differs) | 2026-11-10 (better) | 2026-11-07 (worse) |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/veeam-v0.1.9/veeam-mcp.mcpb) | Remote server (innovint.usefulapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 3 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 6 | 11 |
| First seen (differs) | 2026-10-11 | 2026-10-30 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 401 |
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
Veeam VSPC MCP
Sync Veeam Service Provider Console tenants to local SQLite; cross-company backup answers offline.
InnoVint MCP by usefulapi
Review winery lots, vessels, analyses and work history; record analyses and add vendors.
How to run each
Veeam VSPC MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install veeam@msp-skillsRequires: PRINTING_PRESS_CLIENT_PROFILE (secret), VEEAM_BASE_URL, VEEAM_MCP_HTTP_TOKEN (secret), VEEAM_TOKEN (secret)
InnoVint MCP by usefulapi As a remote MCP server
claude mcp add --transport http innovint https://innovint.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only InnoVint MCP by usefulapi has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of InnoVint MCP by usefulapi publish no settings it asks for, so we do not compare settings.
What it can do: Veeam VSPC MCP · What it can do: InnoVint MCP by usefulapi · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.