Vibedeploy MCP Server

https://mcp.vibedeploy.be/mcp Remote v1.0.1

Published by mcp.vibedeploy.be — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Deploy and host AI-built websites on EU infrastructure, straight from your AI agent.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: deploy_from_url → read_file ⇒ add_file_chunk. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow deploy_from_url → read_file → add_file_chunk

low Unconstrained path parameter "path" on "read_file"MTC-CAP-008

Tool "read_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool read_file · inputSchema.properties.path

low Unconstrained path parameter "path" on "read_source_file"MTC-CAP-008

Tool "read_source_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool read_source_file · inputSchema.properties.path

Tools 39

Each tool and what it can reach — enumerated from the running server.

  • read_source_fileingests untrusted inputreads sensitive data
  • add_file_chunknetwork egress
  • deploy_from_urlingests untrusted input
  • read_filereads sensitive data
  • read_filesreads sensitive data
  • rehost_imagesingests untrusted input
  • abort_deployno sensitive capability
  • add_custom_domainno sensitive capability
  • add_filesno sensitive capability
  • apply_editsno sensitive capability
Show 29 more tools ↓
  • begin_deployno sensitive capability
  • build_and_deployno sensitive capability
  • check_domain_availabilityno sensitive capability
  • commit_deployno sensitive capability
  • create_snapshotno sensitive capability
  • delete_siteno sensitive capability
  • delete_source_fileno sensitive capability
  • deploy_siteno sensitive capability
  • get_accountno sensitive capability
  • get_forms_configno sensitive capability
  • get_siteno sensitive capability
  • get_site_analyticsno sensitive capability
  • list_custom_domainsno sensitive capability
  • list_deploysno sensitive capability
  • list_dns_recordsno sensitive capability
  • list_file_hashesno sensitive capability
  • list_historyno sensitive capability
  • list_sitesno sensitive capability
  • list_snapshotsno sensitive capability
  • list_source_filesno sensitive capability
  • read_source_filesno sensitive capability
  • remove_custom_domainno sensitive capability
  • search_filesno sensitive capability
  • set_forms_configno sensitive capability
  • update_file_contentno sensitive capability
  • update_siteno sensitive capability
  • verify_custom_domainno sensitive capability
  • verify_forms_sender_domainno sensitive capability
  • write_source_filesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 94/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-vibedeploy-be/badge.svg)](https://mcptrustchecker.com/registry/mcp-vibedeploy-be)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-vibedeploy-be"><img src="https://mcptrustchecker.com/registry/mcp-vibedeploy-be/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-vibedeploy-be/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://mcp.vibedeploy.be/mcp --online

Use the free API → How scoring works

More in Cloud & DevOps