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 (6 minutes 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 →
add_proxy_site ~115
Register a reverse-proxy site: <name>.test forwards to 127.0.0.1:<port> for a server EnvKit does not run (Docker, Go, Rust, .NET…). No project folder, no managed process; provisions the host + SSL.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | optional custom hostname instead of <name>.test |
| name | string | yes | site name (becomes <name>.test) |
| port | string | yes | local port to forward to, 1-65535 |
No output schema declared.
No examples provided.
add_site ~72
Register an existing project folder as a site (auto-detects the framework, then provisions its .test host + SSL). Appears in the app immediately — no restart.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | optional site name (defaults to the folder name) |
| path | string | yes | absolute path to the project directory |
No output schema declared.
No examples provided.
apply ~21
Re-apply config: render service configs, sync hosts + SSL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
apply_project_config ~348
Apply a project's committed envkit.json (at the project root) to its EnvKit site: PHP version, required PHP extensions and php.ini values (schema 2 `php: {version, extensions, ini}`), domain/aliases, databases to create, Laravel scheduler/queue workers, custom processes. An optional envkit.local.json (per developer, not committed) is merged over it; items it decided carry origin:'local'. Node is only checked, never changed. The file only adds and updates — workers/processes/aliases it does not mention are kept. web_server is a GLOBAL switch that affects every site, so it is applied only when its key 'web_server' is named in items. PHP extension/ini items belong to a PHP version: when other sites use that version the item lists them in sharedWith and is applied only when its key (e.g. 'php_extension:intl', 'php_ini:memory_limit') is named in items — tell the user which sites it reaches first. With FrankenPHP as the web server, web requests run FrankenPHP's embedded PHP; the plan reports a version or extension it lacks as blocked. Call with dry_run:true first and show the plan to the user before applying. Returns {applied, skipped, errors} (dry run: the plan with items[] and their state same|change|blocked).
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | only return the plan: what envkit.json would change, nothing is applied |
| items | array | – | plan item keys to apply; default = every applicable change except web_server and PHP extension/ini changes shared with other sites |
| name | string | yes | site name |
No output schema declared.
No examples provided.
backup_site ~82
Create a local zip backup of a site (project files + a logical dump of its detected MySQL/Postgres database). Returns the archive path. Skips node_modules, vendor, .git, storage/logs.
| Name | Type | Req | Description |
|---|---|---|---|
| dest_dir | string | – | optional destination folder (default: <dataDir>/backups/<site>) |
| name | string | yes | site name |
No output schema declared.
No examples provided.
build_site ~33
Run a Node site's production build (npm run build); returns the build status.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
clear_site_cache ~30
Purge a production site's server-side cache and rebuild it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
clone_git_site ~52
Clone a git repo into the projects folder, register it as a site, and install dependencies (composer for PHP).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | optional project name |
| url | string | yes | git clone URL |
No output schema declared.
No examples provided.
config ~14
Read the current EnvKit configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_bedrock_site ~89
Scaffold a new Roots Bedrock (Composer-based WordPress) site with composer create-project roots/bedrock (needs PHP + Composer), served from web/ with wp-admin at /wp/wp-admin/, then prepare it like prepare_bedrock_site. Returns the site list plus a `bedrock` object with url and the prepare result.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | project folder name |
No output schema declared.
No examples provided.
create_codeigniter_site ~75
Scaffold a new CodeIgniter 4 site with composer create-project codeigniter4/appstarter (needs PHP + Composer), then prepare it like prepare_codeigniter_site. Returns the site list plus a `codeigniter` object with url and the prepare result.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | project folder name |
No output schema declared.
No examples provided.
create_database ~46
Create a MySQL/MariaDB database (utf8mb4). The mysql service must be running.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | database name (letters, digits, _ $ -) |
No output schema declared.
No examples provided.
create_db ~80
Create a database on a specific engine. The engine must be running.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | 'mysql' | 'postgres' | 'mongodb' |
| instance | string | – | mysql only: the version of an extra MySQL/MariaDB server (see databases_overview); omit for the main server |
| name | string | yes | database name |
No output schema declared.
No examples provided.
create_empty_site ~28
Create an empty project folder registered as a site.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | project name |
No output schema declared.
No examples provided.
create_laravel_site ~65
Scaffold a new Laravel site (needs PHP + Composer).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | project name |
| starter_kit | string | – | optional Packagist starter kit, e.g. laravel/react-starter-kit (default: plain laravel/laravel) |
No output schema declared.
No examples provided.
create_node_site ~59
Scaffold a new Node/JS site using the official scaffolder. Provisions its .test host + SSL.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | nextjs | nuxtjs | vite | angular | node |
| name | string | yes | project name |
No output schema declared.
No examples provided.
create_site_from_blueprint ~220
Create a new site from a saved blueprint zip: unpacks into the projects dir, optionally creates a MySQL database and rewrites wp-config / Laravel .env, registers the site with HTTPS, and runs an optional post-create command. For a WordPress blueprint that ships no db/*.sql dump, pass admin_user + admin_password + admin_email (and optionally title) to finish the WordPress install too; the result's `blueprint.wordpress` carries outcome/adminUrl/installUrl. Returns sites plus a `blueprint` result with url/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_email | string | – | optional WordPress admin email |
| admin_password | string | – | optional WordPress admin password (8+ characters) |
| admin_user | string | – | optional WordPress admin username |
| blueprint_id | string | yes | blueprint id from list_blueprints |
| db_name | string | – | optional MySQL database name |
| name | string | yes | project folder name |
| title | string | – | optional WordPress site title (default: the folder name) |
No output schema declared.
No examples provided.
create_wordpress_site ~180
Create a WordPress site: downloads WordPress, creates its MySQL database and writes wp-config.php (needs PHP + MySQL installed). Pass admin_user + admin_password + admin_email (and optionally title) to finish the install too, so /wp-admin logs in immediately; otherwise the user completes the setup wizard in the browser. Returns the site list plus a `wordpress` object with url/adminUrl/installUrl/outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_email | string | – | optional admin email |
| admin_password | string | – | optional admin password (8+ characters) |
| admin_user | string | – | optional admin username |
| db_name | string | – | optional MySQL database name (default: derived from the folder name) |
| name | string | yes | project folder name |
| title | string | – | optional site title (default: the folder name) |
No output schema declared.
No examples provided.
create_worktree_site ~109
Check out a branch of a site's repo as a git worktree (in <root>/.worktrees/<branch>, excluded from the parent repo via .git/info/exclude) and serve it as its own site on a subdomain of the parent: https://<branch>.<site>.test. Uses an existing local/remote branch or creates it from HEAD.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | branch name, e.g. feature/login |
| name | string | yes | parent site name |
No output schema declared.
No examples provided.
cron_list ~55
List scheduled tasks (cron jobs). Read-only. A job with `site` belongs to that site; `siteState` other than "active" (disabled / asleep / missing = site removed) means its scheduled runs are skipped.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cron_remove ~23
Delete a scheduled task.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | cron job id |
No output schema declared.
No examples provided.
cron_run ~24
Run a scheduled task now.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | cron job id |
No output schema declared.
No examples provided.
cron_save ~127
Create or update a scheduled task. job: {id?, name, schedule (5-field cron), command, cwd?, site?, enabled?}. `site` links the job to a site by name: it runs in the site folder when cwd is empty and is skipped while the site is disabled or asleep; null unlinks, omitting it keeps the current link. For Laravel `schedule:run` prefer set_site_scheduler (the site's built-in scheduler) over a cron job.
| Name | Type | Req | Description |
|---|---|---|---|
| job | object | yes | { id?, name, schedule, command, cwd?, site?, enabled? } |
No output schema declared.
No examples provided.
databases_overview ~46
Per-engine database list + status and ordered adminUis across MySQL/MariaDB, PostgreSQL, MongoDB. The legacy adminUi field remains the primary UI. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
db_connections ~33
Connection details (host/port/user) for each running DB engine, for copying into a project .env. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
debug_tail ~124
Read recent Debug-window events captured from a site (dump()/dd(), SQL queries with N+1/slow flags, mail, rendered views, dispatched events, queued jobs, outgoing HTTP). Scoped per site and per git branch. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | git branch to scope to (optional; defaults to all branches) |
| limit | number | – | max events (default 100) |
| name | string | yes | site name |
| type | string | – | filter by type: dump|query|mail|view|event|job|http (optional) |
No output schema declared.
No examples provided.
default_php ~14
Get the default PHP version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dev_tools_status ~33
Install status of the managed developer tools: Composer, PIE, Git, GitHub CLI, Laravel installer. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
diagnose_service ~41
Diagnose why a service won't start (port conflict, missing config/dir, stale pid, log errors). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | service name |
No output schema declared.
No examples provided.
drop_database ~41
Drop a MySQL/MariaDB database (destructive — system schemas are refused). Confirm intent with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | database name |
No output schema declared.
No examples provided.
drop_db ~82
Drop a database on a specific engine (destructive — system schemas refused). Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | 'mysql' | 'postgres' | 'mongodb' |
| instance | string | – | mysql only: the version of an extra MySQL/MariaDB server; omit for the main server |
| name | string | yes | database name |
No output schema declared.
No examples provided.
dumps_tail ~95
Read recent dump()/dd() output from the Dumps page, across every PHP site or one site (newest last; `data.text` is the plain-text dump, `source` the file:line). Capture must be on for the site (set_site_dumps). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | max dumps (default 500) |
| site | string | – | site name (optional; defaults to every site) |
No output schema declared.
No examples provided.
export_project_config ~139
Write a site's current EnvKit setup (PHP major.minor, Node from .nvmrc, custom domain, aliases, detected databases, scheduler, queue workers, processes) to envkit.json at the project root, so teammates can apply it. Never writes the web server; process env variables are written by name with an empty value (never the value). Queue worker extraArgs are written as configured, so review the file before committing it. Refuses to replace an existing envkit.json unless overwrite is true — ask the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
| overwrite | boolean | – | replace an existing envkit.json |
No output schema declared.
No examples provided.
get_site_workers ~33
Get queue worker, scheduler, and custom process runtime status for a site.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
git_action ~107
Run a Git action on a site: pull|push|fetch|stageAll|stage|unstage|discardFile|commit|checkout|createBranch. payload: {file?, message?, all?, branch?}.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | pull|push|fetch|stageAll|stage|unstage|discardFile|commit|checkout|createBranch |
| name | string | yes | site name |
| payload | object | – | { file?, message?, all?, branch? } |
No output schema declared.
No examples provided.
git_overview ~46
Git snapshot for a site: branch, ahead/behind, changed files (staged/unstaged), and recent commits. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
help ~130
Answer "how do I / where is / can I …" questions about USING EnvKit itself — features, where each setting lives, and step-by-step how-tos (e.g. change the default editor → Settings → Startup; add a custom service version; enable a database admin UI; put tools on PATH). Read-only. Call this for ANY question about the app's UI / features / settings, optionally with a `topic` keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | optional keyword to focus on, e.g. "editor", "php", "path", "ssl", "database", "cron" |
No output schema declared.
No examples provided.
install_dev_tool ~48
Install a managed developer tool and put it on PATH.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | 'composer' | 'pie' | 'git' | 'gh' | 'laravel-installer' |
No output schema declared.
No examples provided.
install_php_extension ~88
Download + install a PECL extension build matching the PHP version (e.g. xdebug, redis, imagick), then enable it. Also accepts the encoded-PHP loaders "ioncube" (Windows) and "sourceguardian" (Windows x64, macOS arm64).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | PECL extension name |
| version | string | – | PHP version (optional) |
No output schema declared.
No examples provided.
install_service ~56
Download + install a bundled service version (nginx/php/mysql/postgres/redis/mongodb/node/…). Use list_services for ids/versions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | service id |
| version | string | yes | version to install |
No output schema declared.
No examples provided.
issue_letsencrypt ~81
Issue a Let's Encrypt certificate for a site's real (public) domain. opts: {challenge:'http-01'|'dns-01', email?, dnsProvider?, cloudflareToken?, staging?}.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
| opts | object | yes | { challenge, email?, dnsProvider?, cloudflareToken?, staging? } |
No output schema declared.
No examples provided.
laragon_detect ~35
Detect a Laragon install (projects, PHP, Node, databases).
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | Laragon root (optional) |
No output schema declared.
No examples provided.
list_blueprints ~24
List saved project blueprints (user zip templates for one-click site creation).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_database_snapshots ~68
List the snapshots of a database, newest first (id, createdAt, size, source instance/port) as {snapshots:[...]}. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | 'mysql' | 'postgres' (default mysql) |
| name | string | yes | database name |
No output schema declared.
No examples provided.
list_databases ~21
List databases on the running MySQL/MariaDB server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_logs ~53
List available log sources. `logical: true` sources follow the newest file of a daily-rotated log (e.g. Laravel laravel-YYYY-MM-DD.log); `path` is the file they currently read.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~17
List bundled services with install + runtime status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_site_backups ~40
List local zip backups for a site (path, size, createdAt, databases included). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
list_site_scripts ~48
List a site's package.json scripts, the detected package manager (npm/pnpm/yarn/bun, or deno) and the exact install command.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | site name |
No output schema declared.
No examples provided.
list_sites ~14
List all registered sites/projects.
Input schema present but exposes no named parameters.
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.