io.github.CloudCorpRecords/deployport
NPM · @RENETURCIOS/DEPLOYPORT · 2 COMPONENTS
Vercel projects, deployments, domains and env vars as MCP tools.
Available components
Last scanned (5 hours ago)
Scores higher than 32% of npm servers
Category CI/CD and DevOps
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 Security81
- 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
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 (MIT).Pass
- Actively maintained (last published 3 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 507 tokens (~42/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project" implies "delete" 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 12 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 63
First indexed and scored.
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 npm/@reneturcios/deployport@0.1.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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
cancel_deployment ~35
Cancel a Vercel deployment by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | ID of the Vercel deployment to cancel. |
No output schema declared.
No examples provided.
create_deployment ~78
Create a Vercel deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the project to deploy. |
| project | string | – | Identifier of the project to create the deployment for; omit to let Vercel resolve it from the name. |
| target | string | – | Deployment target, such as production or preview; omit for the default target. |
No output schema declared.
No examples provided.
create_project ~61
Create a Vercel project.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Framework preset to configure for the new project (e.g. nextjs); omit to let Vercel detect it. |
| name | string | yes | Name of the Vercel project to create. |
No output schema declared.
No examples provided.
delete_project ~34
Delete a Vercel project by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | ID of the Vercel project to delete. |
No output schema declared.
No examples provided.
get_current_user ~17
Retrieve the current Vercel user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_deployment ~36
Retrieve a single Vercel deployment by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | ID of the Vercel deployment to retrieve. |
No output schema declared.
No examples provided.
get_deployment_events ~38
List events for a Vercel deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | ID of the Vercel deployment whose events to list. |
No output schema declared.
No examples provided.
get_project ~35
Retrieve a single Vercel project by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | ID of the Vercel project to retrieve. |
No output schema declared.
No examples provided.
list_deployments ~79
List Vercel deployments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of deployments to return. |
| project_id | string | – | Only return deployments for this Vercel project ID; omit to list deployments across projects. |
| target | string | – | Only return deployments with this target (e.g. production or preview); omit for all targets. |
No output schema declared.
No examples provided.
list_domains ~27
List Vercel domains.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of domains to return. |
No output schema declared.
No examples provided.
list_project_env_vars ~40
List environment variables for a Vercel project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | ID of the Vercel project whose environment variables to list. |
No output schema declared.
No examples provided.
list_projects ~27
List Vercel projects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of projects to return. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/deployport MCP server?
io.github.CloudCorpRecords/deployport runs locally as an npm package, launched with npx -y @reneturcios/deployport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/deployport
claude mcp add cloudcorprecords-deployport -- npx -y @reneturcios/deployport
What is the io.github.CloudCorpRecords/deployport MCP server?
io.github.CloudCorpRecords/deployport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/deployport. Vercel projects, deployments, domains and env vars as MCP tools. This page covers its npm package (@reneturcios/deployport).
Is the io.github.CloudCorpRecords/deployport MCP server safe to use?
io.github.CloudCorpRecords/deployport scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.CloudCorpRecords/deployport MCP server expose?
io.github.CloudCorpRecords/deployport exposes 12 tools: list_projects, get_project, create_project, delete_project, list_deployments, and 7 more. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/deployport MCP server still maintained?
io.github.CloudCorpRecords/deployport 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 io.github.CloudCorpRecords/deployport MCP server under?
io.github.CloudCorpRecords/deployport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.