Proximo — the governed client for Proxmox
PYPI · PROXIMO-PROXMOX
The governed client for Proxmox (PVE, PBS, PMG, PDM): plans, keeps the receipts, puts things back.
Available components
Last scanned (14 hours ago)
Scores higher than 86% of PyPI servers
Category Cloud Infrastructure
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to john-broadway/proximo). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 647 tokens (~107/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management29
- Stability check failed: the tool surface changed between 0.44.1 and 0.51.0: 3 tool removals, 4 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Licence: Apache-2.0 → AGPL-3.0-or-later functional
- Package version: 0.50.1 → 0.51.0 functional
- 29 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.50.0 → 0.50.1 functional
- 28 Oct 26 0
- Package version: 0.49.1 → 0.50.0 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.48.1 → 0.49.1 functional
- Package version: 0.44.2 → 0.49.0 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 0
- Package version: 0.47.0 → 0.48.1 functional
- Package version: 0.47.0 → 0.48.0 functional
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 5 Nov 2026 · Analysed pypi/proximo-proxmox@0.51.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | john-broadway/proximo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/john-broadway/proximo/.github/workflows/release-pypi.yml@refs/tags/v0.51.0 |
| Rekor log index | 3635591569 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:baf08150f36f1922b190e39c8391a87fcd7defaeb44508171d3bb0cb80c661d1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_entries ~56
READ-ONLY: the PROVE ledger, newest first, bounded; says when it truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| limit | integer | – | – |
| mutations_only | boolean | – | – |
| target | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
audit_verify ~52
READ-ONLY: walk the chain, report the first break; expected_head catches a cut tail; path=<archive> checks a sealed archive.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_head | string | – | – |
| path | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
proximo_call ~167
MUTATION: run a governed POST/PUT/DELETE. Without confirm=true it returns the plan (verdict, consent id, current, change) and mutates nothing. Refused unless the operator is armed AND the address has an authored blast-radius tier. Every call, refused or executed, is receipted. Task-backed calls are waited on (wait=N s, default 60, max 600; 0 submits only). method=undo with path=<undo.id> puts a receipt's capture back, plan first; withheld or unpublished keys come back as skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | – |
| confirm | boolean | – | – |
| method | string | yes | – |
| path | string | yes | – |
| plane | string | yes | – |
| wait | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
proximo_find ~64
READ-ONLY: find API addresses by plain words ('list datastores'). A verb picks the method. Returns access and blast-radius tier. 5 by default.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| plane | string | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
proximo_plan ~134
READ-ONLY, mutates nothing: the governed verdict (armed, tier, consent) for one address, with the parameters you gave and the required ones you lack; fields='name1,name2' or 'all' shows the vendor's full schema. A mutation's plan also reads the target: current, change, noop. Run before proximo_call. path may be words: one match is planned, several come back to pick from.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | – |
| fields | string | – | – |
| method | string | yes | – |
| path | string | yes | – |
| plane | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
proximo_read ~174
READ-ONLY: run a GET by path or words (no leading slash). args = query parameters (params: old name). Rows come lean with a total; fields='all' or 'name,status' for others; over the cap you get counts and a next line. since='24h': what changed, from the door's snapshots. wait=N on .../tasks/{upid}/status waits up to N s (max 600). diagnose=true on a node or guest path: health and advisory flags. Credentials come back withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | – |
| diagnose | boolean | – | – |
| fields | string | – | – |
| params | object | – | – |
| path | string | yes | – |
| plane | string | yes | – |
| since | string | – | – |
| wait | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Proximo — the governed client for Proxmox MCP server?
Proximo — the governed client for Proxmox runs locally as a PyPI package, launched with uvx proximo-proxmox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · proximo-proxmox
claude mcp add john-broadway-proximo-proxmox -- uvx proximo-proxmox
What is the Proximo — the governed client for Proxmox MCP server?
Proximo — the governed client for Proxmox is an MCP server listed in the public MCP registry as io.github.john-broadway/proximo-proxmox. The governed client for Proxmox (PVE, PBS, PMG, PDM): plans, keeps the receipts, puts things back. This page covers its PyPI package (proximo-proxmox).
Is the Proximo — the governed client for Proxmox MCP server safe to use?
Proximo — the governed client for Proxmox scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Proximo — the governed client for Proxmox MCP server expose?
Proximo — the governed client for Proxmox exposes 6 tools: proximo_find, proximo_plan, proximo_read, proximo_call, audit_entries, audit_verify. Their descriptions and schemas cost roughly 647 tokens of context every time the server is loaded.
Is the Proximo — the governed client for Proxmox MCP server still maintained?
Proximo — the governed client for Proxmox is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Proximo — the governed client for Proxmox MCP server under?
Proximo — the governed client for Proxmox declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Proximo — the governed client for Proxmox MCP server?
VerifyMCP ran 16 checks on Proximo — the governed client for Proxmox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.