io.github.przemekzur/breezedeploy
NPM · BREEZEDEPLOY-MCP
Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.
Available components
Last scanned (21 hours ago)
Scores higher than 44% of npm 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 933 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_app" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 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.
- 9 Nov 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.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/breezedeploy-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 34 |
| 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 →
add_database Add a Postgres database ~45
Provision a managed Postgres database for a project. New deployments in the project automatically receive its connection string as DATABASE_URL.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name (created if new) |
No output schema declared.
No examples provided.
delete_app Stop/delete an app ~38
Stop a deployed app by project and app name.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name to stop |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
deploy_app Deploy an app from a Docker image ~147
Deploy a container image to a project and get a live HTTPS URL. Creates the project if it does not exist. Use `mode: autoscale` (default, sleeps when idle) or `reserved` (always on).
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name; becomes the subdomain |
| env | object | – | Environment variables |
| image | string | yes | Public Docker image, e.g. nginxdemos/hello |
| mode | string | – | autoscale | reserved |
| port | integer | – | Container port (default 8080) |
| project | string | yes | Project name (created if new) |
| size | string | – | A size key from list_sizes |
No output schema declared.
No examples provided.
deploy_from_git Build and deploy from a git repo ~231
Build a git repository with Nixpacks and deploy it, returning a live HTTPS URL. Use this when the user already has a repo URL; for a plain local folder with no repo, use `deploy_source` instead. Creates the project if it does not exist. For a PRIVATE repo, pass `token` (e.g. a GitHub personal access token) — it's used only to clone and is never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name; becomes the subdomain |
| env | object | – | Environment variables |
| mode | string | – | autoscale | reserved |
| port | integer | – | Container port (default 8080) |
| project | string | yes | Project name (created if new) |
| ref | string | – | Branch, tag, or commit (default: repo default) |
| repoUrl | string | yes | Git repo URL (public, or private with a token) |
| size | string | – | A size key from list_sizes |
| token | string | – | Access token for a PRIVATE https repo (e.g. GitHub PAT). Not stored. |
No output schema declared.
No examples provided.
deploy_source Deploy a local folder (no git, no Docker) ~186
Deploy a local project folder — no git, no Docker, no Dockerfile. Uploads the folder and builds it server-side with Nixpacks, returning a live HTTPS URL. Use this when the user just has a local app on disk (the default, zero-setup path). heavy/secret files (node_modules, .git, dist, build, .env) are excluded automatically. Creates the project if it does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name; becomes the subdomain |
| dir | string | – | Local folder to deploy (default: current directory) |
| env | object | – | Environment variables |
| mode | string | – | autoscale | reserved |
| port | integer | – | Container port (default 8080) |
| project | string | yes | Project name (created if new) |
| size | string | – | A size key from list_sizes |
No output schema declared.
No examples provided.
list_apps List deployed apps ~32
List the deployments (apps) in a project, with status and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
list_plans List billing plans ~22
List billing plans (price, included allotment, overage).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sizes List machine sizes ~18
List available machine sizes and their compute-unit rates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_compliance Generate GDPR compliance docs ~171
Generate and publish imprint, privacy policy, and a cookie-consent banner for a project. Returns public URLs you can link to / embed. Templates only, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | yes | Country of the responsible party |
| string | yes | Contact email | |
| legalName | string | yes | Person or company responsible |
| postalCode | string | – | – |
| processors | array | – | Third-party processors, e.g. Stripe |
| project | string | yes | Project name (created if new) |
| siteName | string | yes | Public site/app name |
| street | string | – | – |
| usesAnalytics | boolean | – | Site uses analytics |
| usesCookies | boolean | – | Site sets non-essential cookies |
| vatId | string | – | – |
No output schema declared.
No examples provided.
usage Usage and cost ~21
Show metered compute units and the current cost estimate for your account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami Account info ~22
Show the resolved tenant and control-plane URL (for debugging the connection).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.przemekzur/breezedeploy MCP server?
io.github.przemekzur/breezedeploy runs locally as an npm package, launched with npx -y breezedeploy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · breezedeploy-mcp
claude mcp add przemekzur-breezedeploy -- npx -y breezedeploy-mcp
What is the io.github.przemekzur/breezedeploy MCP server?
io.github.przemekzur/breezedeploy is an MCP server listed in the public MCP registry as io.github.przemekzur/breezedeploy. Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat. This page covers its npm package (breezedeploy-mcp).
Is the io.github.przemekzur/breezedeploy MCP server safe to use?
io.github.przemekzur/breezedeploy scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.przemekzur/breezedeploy MCP server expose?
io.github.przemekzur/breezedeploy exposes 11 tools: whoami, list_sizes, list_plans, deploy_app, deploy_source, and 6 more. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.
Is the io.github.przemekzur/breezedeploy MCP server still maintained?
io.github.przemekzur/breezedeploy is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.przemekzur/breezedeploy MCP server under?
io.github.przemekzur/breezedeploy declares the MIT 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.przemekzur/breezedeploy MCP server?
VerifyMCP ran 15 checks on io.github.przemekzur/breezedeploy, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.przemekzur/breezedeploy: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.