EnvKit
MCPB · ENVKIT-MCP-0.33.0-BETA.44.MCPB
Control the EnvKit local dev stack (PHP, nginx, MySQL, sites). Requires the EnvKit desktop app.
Available components
Last scanned (1 hour ago)
Scores higher than 74% 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 & Transparency32
- 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
- License check failed: the license (Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 7965 tokens (~72/item across 110 items; 110 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 4 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nvm_uninstall" implies "uninstall" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 111 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 6 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.17 ▲ 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 6 Nov 2026 · Analysed mcpb/https://github.com/Env-Kit/envkit-releases/releases/download/v0.33.0-beta.44/envkit-mcp-0.33.0-beta.44.mcpb@0.33.0-beta.44
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 →
status ~57
FULL EnvKit status: services, sites, SSL trust, port conflicts, and the whole bundled catalog with every installable version. Heavy — prefer status_live for routine checks; call this only when you need catalog/SSL/port-conflict detail.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
status_live ~50
Fast runtime snapshot: running services, sites, ports — the same cheap poll the dashboard uses (no cert checks, no port-conflict scan, no catalog). Prefer this over `status` for routine checks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stop_all ~12
Stop all services.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stop_mysql_version ~54
Stop one MySQL/MariaDB version. Stopping the active version stops the main server; stopping another keeps its port reserved.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | yes | full version, e.g. 5.7.44 |
No output schema declared.
No examples provided.
stop_service ~22
Stop a running service.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | service name |
No output schema declared.
No examples provided.
stop_share ~43
Stop a public share and release its tunnel. Stops every share when no site name is given.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | site name (optional; omit to stop all) |
No output schema declared.
No examples provided.
tail_log ~89
Read the last N lines of a log source. Returns { lines, truncated, size, bytesRead, file }: truncated "lines" = older lines exist, "bytes" = the read budget ran out before N lines (very long records), "none" = the whole file is shown.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | log source id |
| lines | number | – | lines (default 100) |
No output schema declared.
No examples provided.
tinker_eval ~45
Run PHP/Laravel Tinker code in a site and return the output.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | PHP code to evaluate |
| name | string | yes | site name |
No output schema declared.
No examples provided.
uninstall_service ~64
Uninstall a bundled service (removes its files; destructive). Pass version to remove only that version, leaving other installed versions intact.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | service id |
| version | string | – | version to remove (default: the whole service, every installed version) |
No output schema declared.
No examples provided.
wake_site ~74
Wake a sleeping site: restart its background processes. Pass minutes=60 to put it back to sleep after an hour without visits. Returns the site detail.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | number | – | optional: 60 = go back to sleep after an hour without visits; omit to stay awake |
| name | string | yes | site name |
No output schema declared.
No examples provided.
How do I install the EnvKit MCP server?
EnvKit 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, 47c45be8c6eab6370a50c7b57c25c0990233e9b76b4c676ecbd38daa7c43362a; the commands to do that are on this page. If it does not match, do not open it.
mcpb · envkit-mcp-0.33.0-beta.44.mcpb
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
47c45be8c6eab6370a50c7b57c25c0990233e9b76b4c676ecbd38daa7c43362a
macOS / Linux
echo "47c45be8c6eab6370a50c7b57c25c0990233e9b76b4c676ecbd38daa7c43362a envkit-mcp-0.33.0-beta.44.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\envkit-mcp-0.33.0-beta.44.mcpb).Hash -eq "47c45be8c6eab6370a50c7b57c25c0990233e9b76b4c676ecbd38daa7c43362a"
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 EnvKit MCP server?
EnvKit is an MCP server listed in the public MCP registry as io.github.Env-Kit/envkit. Control the EnvKit local dev stack (PHP, nginx, MySQL, sites). Requires the EnvKit desktop app. This page covers its MCPB bundle (https://github.com/Env-Kit/envkit-releases/releases/download/v0.33.0-beta.44/envkit-mcp-0.33.0-beta.44.mcpb).
Is the EnvKit MCP server safe to use?
EnvKit scores 43 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 EnvKit MCP server expose?
EnvKit exposes 110 tools: help, status, status_live, config, paths, and 105 more. Their descriptions and schemas cost roughly 7,656 tokens of context every time the server is loaded.
What licence is the EnvKit MCP server under?
EnvKit declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the EnvKit MCP server?
VerifyMCP ran 12 checks on EnvKit, 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 EnvKit: 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.