Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/sitehost-port

NPM · @RENETURCIOS/SITEHOST-PORT · 2 COMPONENTS

Netlify sites, deploys and builds as MCP tools.

63 Trust /100

Last scanned (11 hours ago)

Scores higher than 31% of npm servers

Category CI/CD and DevOps

Trust breakdown (7 categories)

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
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 527 tokens (~43/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_site" 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

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.

Changelog

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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 48

    First indexed and scored.

Diagnostics

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/sitehost-port@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 →

MCP tools · 12 exposed · ~527 tokens

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 →

Tool Tokens
create_site ~30

Create a Netlify site.

NameTypeReqDescription
namestringyesThe name to give the new Netlify site.

No output schema declared.

No examples provided.

delete_site ~34

Delete a Netlify site by ID.

NameTypeReqDescription
site_idstringyesThe unique identifier of the Netlify site to delete.

No output schema declared.

No examples provided.

get_current_user ~16

Retrieve the current Netlify user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_deploy ~36

Retrieve a single Netlify deploy by ID.

NameTypeReqDescription
deploy_idstringyesThe unique identifier of the Netlify deploy to retrieve.

No output schema declared.

No examples provided.

get_site ~35

Retrieve a single Netlify site by ID.

NameTypeReqDescription
site_idstringyesThe unique identifier of the Netlify site to retrieve.

No output schema declared.

No examples provided.

list_deploys ~73

List deploys for a Netlify site.

NameTypeReqDescription
pagenumber–Optional page number of deploys to return.
per_pagenumber–Optional maximum number of deploys to return per page.
site_idstringyesThe unique identifier of the Netlify site whose deploys to list.

No output schema declared.

No examples provided.

list_env_vars ~39

List environment variables for a Netlify site.

NameTypeReqDescription
site_idstringyesThe unique identifier of the Netlify site whose environment variables to list.

No output schema declared.

No examples provided.

list_site_builds ~55

List builds for a Netlify site.

NameTypeReqDescription
per_pagenumber–Optional maximum number of builds to return per page.
site_idstringyesThe unique identifier of the Netlify site whose builds to list.

No output schema declared.

No examples provided.

list_sites ~59

List Netlify sites.

NameTypeReqDescription
namestring–Optional site name to filter the list by.
pagenumber–Optional page number of sites to return.
per_pagenumber–Optional maximum number of sites to return per page.

No output schema declared.

No examples provided.

restore_deploy ~33

Restore a Netlify deploy.

NameTypeReqDescription
deploy_idstringyesThe unique identifier of the Netlify deploy to restore.

No output schema declared.

No examples provided.

trigger_site_build ~55

Trigger a build for a Netlify site.

NameTypeReqDescription
branchstring–Optional branch to build; omitted from the request when not provided.
site_idstringyesThe unique identifier of the Netlify site to build.

No output schema declared.

No examples provided.

update_site ~62

Update a Netlify site by ID.

NameTypeReqDescription
custom_domainstring–Optional new custom domain for the site.
namestring–Optional new name for the site.
site_idstringyesThe unique identifier of the Netlify site to update.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/sitehost-port MCP server?

io.github.CloudCorpRecords/sitehost-port runs locally as an npm package, launched with npx -y @reneturcios/sitehost-port. 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/sitehost-port

# add to Claude Code
claude mcp add cloudcorprecords-sitehost-port -- npx -y @reneturcios/sitehost-port
Common questions

What is the io.github.CloudCorpRecords/sitehost-port MCP server?

io.github.CloudCorpRecords/sitehost-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sitehost-port. Netlify sites, deploys and builds as MCP tools. This page covers its npm package (@reneturcios/sitehost-port).

Is the io.github.CloudCorpRecords/sitehost-port MCP server safe to use?

io.github.CloudCorpRecords/sitehost-port scores 63 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/sitehost-port MCP server expose?

io.github.CloudCorpRecords/sitehost-port exposes 12 tools: list_sites, get_site, create_site, update_site, delete_site, and 7 more. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/sitehost-port MCP server still maintained?

io.github.CloudCorpRecords/sitehost-port 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/sitehost-port MCP server under?

io.github.CloudCorpRecords/sitehost-port declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.