io.github.piotrkowalczuk/zordon
MCPB · UNIVERSAL
Supervise a local dev stack — databases, brokers and services declared in an Alphasfile — over MCP.
Available components
Last scanned (18 hours ago)
Scores higher than 82% of MCPB 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- 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 (GPL-3.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1098 tokens (~122/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −5
- Stability: pass → 0.60 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 5 Nov 2026 · Analysed mcpb/https://github.com/piotrkowalczuk/zordon/releases/download/v0.28.1/zordon_0.28.1_universal.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| 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 →
clean ~105
run each provision's clean teardown snippet for the invocation level; the stack must be stopped first (or use zordon stop --clean) Usage: zordon clean [FLAGS] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
get ~100
print a resolved value (dotted path or Go template) e.g. service.go.prometheus.vars.address Usage: zordon get <expr> Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
pkg ~96
manage the versions of the remote repositories the Alphasfile imports Usage: zordon pkg <get|update> [args] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
plan ~125
render the resolved Alphasfile chain with every interpolation baked to a concrete value (--services/ZORDON_SERVICES or positional args render just that subset of the invocation level); errors on the first unresolvable expression Usage: zordon plan [FLAGS] [service ...] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
start ~109
ensure alpha is running and push the Alphasfile config (--services/ZORDON_SERVICES or positional args bring up just that subset) Usage: zordon start [FLAGS] [service ...] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
status ~99
query the running alpha for its state (--format text, agent or json; see docs/reference/status-formats.md) Usage: zordon status Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
stop ~101
ask the running alpha to shut down (--clean also runs each provision's clean snippet once the stack is down) Usage: zordon stop [--clean] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
sudo ~89
run the idempotent privileged hooks for the whole federation chain Usage: zordon sudo Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
workspace ~104
manage parallel workspaces (isolated state/ports over the same Alphasfile) Usage: zordon workspace <create|list|rm|service> [args] Pass flags and positional args via the `args` array; call with ["-h"] for the full flag list.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | command-line flags and positional arguments for the subcommand, e.g. ["--failfast=false","web"]; pass ["-h"] for full help |
No output schema declared.
No examples provided.
How do I install the io.github.piotrkowalczuk/zordon MCP server?
io.github.piotrkowalczuk/zordon ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 625fd4991c5f04b4eb52c4e0b09d9c1c59380f3b68680d138ffa54e58a4c57b3; the commands to do that are on this page. If it does not match, do not open it.
mcpb · universal
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
625fd4991c5f04b4eb52c4e0b09d9c1c59380f3b68680d138ffa54e58a4c57b3
macOS / Linux
echo "625fd4991c5f04b4eb52c4e0b09d9c1c59380f3b68680d138ffa54e58a4c57b3 zordon_0.28.1_universal.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\zordon_0.28.1_universal.mcpb).Hash -eq "625fd4991c5f04b4eb52c4e0b09d9c1c59380f3b68680d138ffa54e58a4c57b3"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the io.github.piotrkowalczuk/zordon MCP server?
io.github.piotrkowalczuk/zordon is an MCP server listed in the public MCP registry as io.github.piotrkowalczuk/zordon. Supervise a local dev stack, databases, brokers and services declared in an Alphasfile, over MCP. This page covers its MCPB bundle (https://github.com/piotrkowalczuk/zordon/releases/download/v0.28.1/zordon_0.28.1_universal.mcpb).
Is the io.github.piotrkowalczuk/zordon MCP server safe to use?
io.github.piotrkowalczuk/zordon 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 io.github.piotrkowalczuk/zordon MCP server expose?
io.github.piotrkowalczuk/zordon exposes 9 tools: clean, get, pkg, plan, start, and 4 more. Their descriptions and schemas cost roughly 928 tokens of context every time the server is loaded.
What licence is the io.github.piotrkowalczuk/zordon MCP server under?
io.github.piotrkowalczuk/zordon declares the GPL-3.0 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 io.github.piotrkowalczuk/zordon MCP server?
VerifyMCP ran 12 checks on io.github.piotrkowalczuk/zordon, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.piotrkowalczuk/zordon: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.