VibeDeploy MCP server
be.vibedeploy/vibedeployvibedeploy.bestreamable-httpv1.1.0Scanned
Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.
43 tools: 16 can delete or cancel things, 1 do something that can't be undone, 8 change things and 18 only read.
- Reads private data · 12
- Reads text others write · 27
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
16 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the VibeDeploy MCP server can do
The VibeDeploy MCP server is published by vibedeploy.be, a domain the MCP Registry verified. It has 43 tools. It can delete or cancel things (16 tools: deploy_site, update_site, delete_site, write_source_files and 12 more), do things that cannot be undone, such as sending, paying or publishing (add_file_chunk) and create or change data (8 tools: promote_dist_to_source, verify_forms_sender_domain, add_custom_domain, verify_custom_domain and 4 more). 18 tools only read.
12 tools read private data (get_site, read_file, read_files and 9 more); 27 tools bring in text other people can write (deploy_site, update_site, list_sites and 24 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
43 tools
Deletes or cancels 16Claude Code: deny
apply_editsApply literal find/replace edits to several files in one call, in the served files (target 'dist', live at once) or the editable source (target 'source', shipped by build_and_deplo…Reads text others writeNo findings
Why it is in this group
- The name "apply_edits" says "apply": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Apply literal find/replace edits to several files in one call, in the served files (target 'dist', live at once) or the editable source (target 'source', shipped by build_and_deploy). Same edit rules as update_file_content. All or nothing: if any edit's match count differs from its expected count, no file is written.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
build_and_deployBuild the site's stored editable source in an isolated one-shot build pod and atomically publish the output as the live site, replacing the served files (a restore point is normall…Reads text others writeNo findings
Why it is in this group
- The name "build_and_deploy" says "deploy": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Build the site's stored editable source in an isolated one-shot build pod and atomically publish the output as the live site, replacing the served files (a restore point is normally taken first). Use build_and_deploy after changing stored source (write_source_files, apply_edits with target 'source'); use update_site instead to upload files that are already built. The first build saves buildCommand, outputDir and rootPath on the site, so later calls can omit them. A failed build returns its log in the error details.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
commit_deployPublish a begin_deploy session's staged files to the live site in one atomic step, after a secret and malware scan of the complete set (on failure the session stays open to retry o…Reads text others writeNo findings
Why it is in this group
- The name "commit_deploy" says "commit": a word for a change.
- The description's first verb is "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Publish a begin_deploy session's staged files to the live site in one atomic step, after a secret and malware scan of the complete set (on failure the session stays open to retry or abort). Replace mode on a site that has files needs confirm:"I-want-to-replace-all-files". After a timeout or dropped connection, call it again with the same deployId: it returns the running or finished commit instead of starting a second one. Use commit_deploy only to finish a begin_deploy session; deploy_site and update_site publish in one call.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
create_snapshotTake a point-in-time snapshot of a site's served files, a restore point the user can restore in the VibeDeploy dashboard within the plan's restore window.Reads text others writeNo findings
Why it is in this group
- The name "create_snapshot" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Take a point-in-time snapshot of a site's served files, a restore point the user can restore in the VibeDeploy dashboard within the plan's restore window. Served content does not change, but retention cleanup may remove older snapshots. Container data is not included. Requires an owner or admin team role. NO_VOLUME means the site was never deployed.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
delete_siteSoft-delete a site (confirm:true required).Reads text others writeNo findings
Why it is in this group
- The name "delete_site" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Soft-delete a site (confirm:true required). It stops serving at once and is purged after the plan's restore window (purgesAt in the result); until then the user can restore it in the VibeDeploy dashboard. Use delete_site to remove the whole site; use remove_app instead to stop only its container services.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
delete_source_fileRemove one file from the site's editable source tree.No findings
Why it is in this group
- The name "delete_source_file" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove one file from the site's editable source tree. The served files do not change until build_and_deploy runs.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
deploy_appRun container services next to a site, from any public image: the user's own server (running code from the site's source tree), a database such as Postgres or MySQL, Redis, or work…Reads text others writeNo findings
Why it is in this group
- The name "deploy_app" says "deploy": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Run container services next to a site, from any public image: the user's own server (running code from the site's source tree), a database such as Postgres or MySQL, Redis, or workers, each in a gVisor sandbox. The call applies the whole config: services missing from it are stopped (their volumes are kept) and the others restart, picking up new source files. It waits until every service is ready and returns per-service status; if one is not ready, call get_app_status with logs. One service may be public: it serves the site's HTTP traffic on its port. Use "${generated:NAME}" for database passwords. API keys and other outside secrets never go in the config, the source or the chat: the user adds them in the VibeDeploy dashboard (site Settings, Secrets) and every service receives them as environment variables. Per site: up to 6 services, 2048Mi memory and 2000m CPU in total, 4 volumes, 3Gi storage (VibeDeploy can raise the CPU / memory ceiling of a site; get_app_status shows it as resourceCeilings). Container volumes are not included in snapshots yet.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
deploy_from_urlFetch a public tar(.gz) archive over HTTPS and deploy its files to an existing site in one call (begin_deploy, upload and commit_deploy combined).Reads text others writeNo findings
Why it is in this group
- The name "deploy_from_url" says "deploy": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Fetch a public tar(.gz) archive over HTTPS and deploy its files to an existing site in one call (begin_deploy, upload and commit_deploy combined). Use deploy_from_url when the files are already published at a public URL, such as a repository archive that holds only the built site (no dotfiles), or when your sandbox reaches the allowed hosts (listed under archiveUrl) but not mcp.vibedeploy.be; otherwise use deploy_site or update_site. In replace mode one top-level folder that wraps every file (as in repository archives) is removed, and a site that already has files needs confirm:"I-want-to-replace-all-files". A failed call never leaves a staging session open.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
deploy_sitePublish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.g.Reads text others writeNo findings
Why it is in this group
- The name "deploy_site" says "deploy": a word for a change.
- The description's first verb is "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Publish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.g. {name}.subsite.site). A new name creates the site. An existing name REPLACES EVERY FILE (files not in this call are deleted) and needs confirm:"I-want-to-replace-all-files"; preview with dryRun:true. Use update_site instead to change some files of an existing site. A 100-250 KB text file fits in this call with encoding:'gzip+base64' (gzip locally, then base64); use begin_deploy only when the files do not fit in one call. Ship a top-level 404.html for multi-page sites (otherwise unknown paths serve index.html) and use plain ASCII file names. Afterwards add_custom_domain can serve the site on the user's own domain.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
rehost_imagesDownload the external images a site references (e.g.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Download the external images a site references (e.g. from the old site it was rebuilt from), store them on this VibeDeploy site under assets/img/, and rewrite the HTML <img> references to local paths so the site no longer depends on the original. Call this once AFTER deploying a site rebuilt with the Website Converter. Auto-detects the external image URLs from the site's own HTML; downloads are SSRF-guarded, size/count/time capped, and applied atomically (patch mode). Images already on a VibeDeploy platform domain are skipped.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
remove_appStop every container service of the site; the site serves its static files again.No findings
Why it is in this group
- The name "remove_app" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop every container service of the site; the site serves its static files again. Volumes (database data) are kept unless deleteData is true, which deletes them for good. Use remove_app to stop only the containers; use delete_site to remove the whole site.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
remove_custom_domainDetach a custom domain from a site.Reads text others writeNo findings
Why it is in this group
- The name "remove_custom_domain" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Detach a custom domain from a site. The site itself is unaffected and keeps serving on its platform subdomain (e.g. {name}.subsite.site).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
set_forms_configConfigure the built-in form-to-email relay, fully self-service.No findings
Why it is in this group
- The name "set_forms_config" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Configure the built-in form-to-email relay, fully self-service. Supports a custom From (via a verified sender domain or your own SMTP relay), an explicit Reply-To, and full email branding (subject template, field labels/order, logo, accent color, or a custom HTML body). Requires team role owner or admin. Pass config:null to switch the relay off. If you set a custom `sender` without an `smtpRelay`, the response returns the DNS records to publish; then call verify_forms_sender_domain. Submissions: POST JSON to the returned `endpoint` with Content-Type: application/json (UTF-8). Flat object of form fields (strings/numbers/booleans; checkbox groups may be arrays of strings, joined with ', '). Max 30 fields, 5000 chars/field, 20000 total. Response: {success:true,data:{ok:true}} or {success:false,error:{code,message}}. Rate limit: 10 submits per IP per 10 minutes. Include a hidden honeypot input (default "_gotcha") and leave it empty.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_file_contentApply literal find/replace edits to one file in one call, for small changes where uploading the whole file is wasteful.Reads text others writeNo findings
Why it is in this group
- The name "update_file_content" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Apply literal find/replace edits to one file in one call, for small changes where uploading the whole file is wasteful. Each edit states how many matches it expects; any mismatch aborts the call with no writes. Served-file (dist) edits go live at once; source edits ship with build_and_deploy. Use apply_edits for several files.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
update_siteChange files on an existing site.Reads text others writeNo findings
Why it is in this group
- The name "update_site" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Change files on an existing site. Default mode 'patch' writes only the listed files and keeps the rest; `delete: [paths]` removes files. mode:'replace' deletes every file not listed. Preview with dryRun:true. Use deploy_site instead to create a new site. A 100-250 KB text file fits in one call with encoding:'gzip+base64' (gzip locally, then base64); prefer that over begin_deploy plus add_file_chunk. Fails with SITE_NOT_FOUND when the site does not exist.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
write_source_filesWrite or overwrite files in the site's editable source tree (the first write creates it).Reads text others writeNo findings
Why it is in this group
- The name "write_source_files" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Write or overwrite files in the site's editable source tree (the first write creates it). The served files do not change until build_and_deploy runs. Use list_source_files first to see what exists. A legacy site without source storage returns SOURCE_STORAGE_NOT_ENABLED; the user can ask VibeDeploy support to enable it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Can't be undone 1Claude Code: ask
add_file_chunkSend one file in several calls when it is too big for a single tool call.Reads text others writeNo findings
Why it is in this group
- The name "add_file_chunk" says "add": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Send one file in several calls when it is too big for a single tool call. Last resort: first try add_files with encoding:'gzip+base64' (about 250 KB of text in one call), begin_deploy's uploadUrl (one 100 MB tar POST) or deploy_from_url (public archive URL). When chunking, gzip+base64 each chunk too, mark the first with isFirst and the last with isLast, and send chunks of one file one after another: parallel chunks corrupt it. After a transport error, do not resend the chunk blindly: restart the file from its first chunk (isFirst truncates it).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 8Claude Code: ask
abort_deployDiscard a begin_deploy session and its staged files; the live site is untouched.Reads text others writeNo findings
Why it is in this group
- The name "abort_deploy" says "deploy": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Discard a begin_deploy session and its staged files; the live site is untouched. Cleanup is best effort and retried later if it fails.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
add_custom_domainStart attaching a user-owned domain to an existing site: returns the DNS records the user adds at their DNS provider (a routing record that sends visitors here, plus a TXT that pro…Reads text others writeNo findings
Why it is in this group
- The name "add_custom_domain" says "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start attaching a user-owned domain to an existing site: returns the DNS records the user adds at their DNS provider (a routing record that sends visitors here, plus a TXT that proves ownership). Idempotent: the same siteName and domain return the existing record. Once the records are published (usually minutes, up to 24h), call verify_custom_domain with the returned recordId; VibeDeploy also re-checks automatically for a few days and emails the user when the domain is live. The site must already exist; call deploy_site first if it does not.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
add_filesAdd files to an open begin_deploy session; call it as often as needed, then commit_deploy publishes them together.Reads text others writeNo findings
Why it is in this group
- The name "add_files" says "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Add files to an open begin_deploy session; call it as often as needed, then commit_deploy publishes them together. Paths, extensions and encodings are checked on every call. A 100-250 KB text file usually fits in one call with encoding:'gzip+base64' (gzip locally, then base64); prefer that over add_file_chunk. If your shell can reach mcp.vibedeploy.be, one tar(.gz) POST to begin_deploy's uploadUrl is faster still.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
begin_deployOpen a staging session for a deploy that is too large for one call: stage files with add_files (repeatable), add_file_chunk, or one tar(.gz) POST to the returned uploadUrl, then pu…Reads text others writeNo findings
Why it is in this group
- The name "begin_deploy" says "deploy": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Open a staging session for a deploy that is too large for one call: stage files with add_files (repeatable), add_file_chunk, or one tar(.gz) POST to the returned uploadUrl, then publish with commit_deploy. Use begin_deploy only when the files do not fit in one deploy_site or update_site call. Up to 5 open sessions per token; a session expires after 1 hour.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
check_domain_availabilityCheck whether a domain can be registered and get an indicative price (VAT included where it applies).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check whether a domain can be registered and get an indicative price (VAT included where it applies). Read-only: it never buys, registers or reserves a domain. alternatives:true also checks the same name on be, com, net, eu, nl, io, dev and app. Not tied to a site. The result states whether the user's plan includes buying domains in the dashboard (purchase.dashboardUrl); a domain the user already owns is connected with add_custom_domain.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
promote_dist_to_sourceCreate the editable source tree of a site that has none by copying the files it serves, so later changes can use write_source_files, apply_edits(target:'source') and build_and_depl…No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it Create the editable source tree of a site that has none by copying the files it serves, so later changes can use write_source_files, apply_edits(target:'source') and build_and_deploy. The served files do not change, and a site that already has source is left as is. Use mode 'force' only after telling the user that build output (minified bundles) is not original source.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_custom_domainCheck the records from add_custom_domain (the ownership TXT and the routing record) and, when both are right, start serving the site on that domain; the HTTPS certificate follows a…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check the records from add_custom_domain (the ownership TXT and the routing record) and, when both are right, start serving the site on that domain; the HTTPS certificate follows automatically, usually within a minute or two. If it fails, the result names each record to add, change or remove; DNS changes can take a few minutes to propagate. Calling it again on a verified domain is a harmless re-check.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_forms_sender_domainCheck the DNS records for a site's custom sender domain (DKIM TXT + SPF include).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check the DNS records for a site's custom sender domain (DKIM TXT + SPF include). Once the DKIM record is observed, the sender domain is marked verified and the relay sends from the custom From (DKIM-signed). Until then it falls back to the platform address. DNS can take a few minutes to propagate; re-run if it fails the first time. Not needed when the site uses a custom smtpRelay.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 18Show 18 read-only tools
get_accountReturn the team's plan, its limits, current usage, the trial end date and the per-token MCP rate limit.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Return the team's plan, its limits, current usage, the trial end date and the per-token MCP rate limit. Call it before deploy_site or add_custom_domain to check a plan limit instead of running into PLAN_LIMIT_EXCEEDED.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_app_statusShow the site's container services: per-service status (ready, restarts, waiting or crash reasons, volumes), the stored config, the names of the site secrets that are set (never va…Reads private dataNo findings
Why it is in this group
- The name "get_app_status" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "secret": it reads secrets.
Description, as the server wrote it Show the site's container services: per-service status (ready, restarts, waiting or crash reasons, volumes), the stored config, the names of the site secrets that are set (never values) with the dashboard link where the user adds them, the CPU / memory ceilings of this site (resourceCeilings), and optionally the recent logs of one service. Use get_app_status instead of get_site for anything about containers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_forms_configRead the form-to-email relay config of a site, plus the resolved delivery mode, the active From address, and (for a custom sender domain) the DNS records to publish and their verif…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_forms_config" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "read" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Read the form-to-email relay config of a site, plus the resolved delivery mode, the active From address, and (for a custom sender domain) the DNS records to publish and their verification status. The submission format for the site's form is described under set_forms_config.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_siteReturn one site's details: live URL, status, plan, served file paths, whether editable source is stored (and its build settings), custom domains, bandwidth and the last 10 deploys.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_site" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Return one site's details: live URL, status, plan, served file paths, whether editable source is stored (and its build settings), custom domains, bandwidth and the last 10 deploys. Use get_site to inspect a site before editing it; use list_sites to find site names, and get_app_status for container services.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_site_analyticsReturn a privacy-safe traffic summary for a site over the last `period` days (default 7): total page views, distinct-visitor count, top pages, daily counts, device/browser breakdow…Reads text others writeNo findings
Why it is in this group
- The name "get_site_analytics" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "browser": it reads web pages, which anyone can write.
Description, as the server wrote it Return a privacy-safe traffic summary for a site over the last `period` days (default 7): total page views, distinct-visitor count, top pages, daily counts, device/browser breakdowns, and Web Vitals averages. Never exposes raw visitor IPs or user-agents.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_custom_domainsReturn all custom domains attached to a site, both those added with add_custom_domain (source 'mcp', with a recordId for verify_custom_domain or remove_custom_domain) and those lin…Reads text others writeNo findings
Why it is in this group
- The name "list_custom_domains" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it Return all custom domains attached to a site, both those added with add_custom_domain (source 'mcp', with a recordId for verify_custom_domain or remove_custom_domain) and those linked in the VibeDeploy dashboard (source 'dashboard', verified or removed on the dashboard Web Addresses page at manageUrl). Call it before add_custom_domain to avoid adding a domain twice.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_deploysList the team's begin_deploy staging sessions, by default the active ones (open and committing), up to 50.No findings
Why it is in this group
- The name "list_deploys" says "list": a word for reading.
Description, as the server wrote it List the team's begin_deploy staging sessions, by default the active ones (open and committing), up to 50. Useful after a crash or restart to commit or abort leftovers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_dns_recordsRead the DNS records VibeDeploy tracks for a site (host, type, value), oldest first, including custom-domain verification records.No findings
Why it is in this group
- The name "list_dns_records" says "list": a word for reading.
Description, as the server wrote it Read the DNS records VibeDeploy tracks for a site (host, type, value), oldest first, including custom-domain verification records. Read-only: it never creates, changes or deletes a DNS record.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_file_hashesReturn SHA-256 and size of every served file.Reads private dataNo findings
Why it is in this group
- The name "list_file_hashes" says "list": a word for reading.
What it can reach
- private-dataThe name "list_file_hashes" says "list" and "file": it reads files.
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Return SHA-256 and size of every served file. Before a redeploy, hash your local files, compare, and upload only the changed ones with update_site mode:'patch' or begin_deploy plus add_files.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_historyReturn the site's last 50 deploy and snapshot entries, newest first: how each was triggered, label, snapshot name, file count and secrets detected.Reads private dataNo findings
Why it is in this group
- The name "list_history" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Return the site's last 50 deploy and snapshot entries, newest first: how each was triggered, label, snapshot name, file count and secrets detected. Each entry's snapshot holds the content from BEFORE that entry. Restoring is done by the user in the VibeDeploy dashboard within the plan's restore window; there is no restore tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_sitesList the team's sites (name, URL, status, last deploy), most recently updated first, up to 100.Reads text others writeNo findings
Why it is in this group
- The name "list_sites" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List the team's sites (name, URL, status, last deploy), most recently updated first, up to 100. Use list_sites to find a site name; use get_site for one site's files, source status and history.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_snapshotsList the snapshots of a site's served files (point-in-time restore points).Reads private dataNo findings
Why it is in this group
- The name "list_snapshots" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "file": it reads files.
Description, as the server wrote it List the snapshots of a site's served files (point-in-time restore points). NO_VOLUME means the site was never deployed. Restoring a snapshot is done by the user in the VibeDeploy dashboard within the plan's restore window.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_source_filesList path, SHA-256 and size of every file in the site's editable source tree (the stored pre-build code, not the served files).Reads private dataNo findings
Why it is in this group
- The name "list_source_files" says "list": a word for reading.
What it can reach
- private-dataThe name "list_source_files" says "list" and "file": it reads files.
- private-dataThe description's first sentence says "list" and "file": it reads files.
Description, as the server wrote it List path, SHA-256 and size of every file in the site's editable source tree (the stored pre-build code, not the served files). Read-only. A site without a source tree returns SOURCE_NOT_STORED: write the source with write_source_files, or copy plain static served files with promote_dist_to_source.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_fileReturn one file the site serves now, as text (utf8) or base64 for binary files, e.g.Reads private dataNo findings
Why it is in this group
- The name "read_file" says "read": a word for reading.
What it can reach
- private-dataThe name "read_file" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Return one file the site serves now, as text (utf8) or base64 for binary files, e.g. to edit it and send it back with update_site mode:'patch'. Use read_file for the served files; use read_source_file instead for the editable source tree (get_site.sourceStored). Max 5242880 bytes; get_site.filePaths lists the paths.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_filesRead up to 50 served files in one call, with the same per-file rules as read_file and 8388608 bytes in total; paths past the budget fail with BATCH_BUDGET_EXCEEDED, so request them…Reads private dataNo findings
Why it is in this group
- The name "read_files" says "read": a word for reading.
What it can reach
- private-dataThe name "read_files" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "read" and "file": it reads files.
- private-dataThe input names a file (input.maxBytesPerFile), and the tool reads: it reads files.
Description, as the server wrote it Read up to 50 served files in one call, with the same per-file rules as read_file and 8388608 bytes in total; paths past the budget fail with BATCH_BUDGET_EXCEEDED, so request them again in another call. Use read_source_files instead for the editable source tree.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_source_fileReturn one file from the site's editable source tree (the stored pre-build code), so any chat can edit the site without the original local files.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "read_source_file" says "read": a word for reading.
What it can reach
- private-dataThe name "read_source_file" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "return" and "file": it reads files.
- untrusted-inputThe description's first sentence says "return" and "chat": it reads messages, which other people can write.
Description, as the server wrote it Return one file from the site's editable source tree (the stored pre-build code), so any chat can edit the site without the original local files. list_source_files shows the paths. Use read_source_file for source; use read_file instead for the files the site serves.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_source_filesRead up to 50 files from the editable source tree in one call (8388608 bytes in total).Reads private dataNo findings
Why it is in this group
- The name "read_source_files" says "read": a word for reading.
What it can reach
- private-dataThe name "read_source_files" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "read" and "file": it reads files.
- private-dataThe input names a file (input.maxBytesPerFile), and the tool reads: it reads files.
Description, as the server wrote it Read up to 50 files from the editable source tree in one call (8388608 bytes in total). Each path succeeds or fails on its own; paths past the budget fail with BATCH_BUDGET_EXCEEDED. Use read_source_files for source; use read_files instead for the files the site serves.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_filesSearch every file of a site for a literal string or a regular expression: the served files by default, or the editable source tree with target 'source'.Reads private dataNo findings
Why it is in this group
- The name "search_files" says "search": a word for reading.
What it can reach
- private-dataThe name "search_files" says "search" and "file": it reads files.
- private-dataThe description's first sentence says "search" and "file": it reads files.
Description, as the server wrote it Search every file of a site for a literal string or a regular expression: the served files by default, or the editable source tree with target 'source'. Use it before reading files in bulk, to find the ones that matter.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data12
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write27
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 25
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.vibedeploy.be/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.vibedeploy.be/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 25 tools that change things (16 destructive, 1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.vibedeploy.be/mcp: tools/list returned 43 tools to an anonymous client, including deploy_site (destructive), update_site (destructive), delete_site (destructive), write_source_files (destructive), delete_source_file (destructive) and 20 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:deploy_appDeletes or cancelsdescription
- Changed:deploy_siteDeletes or cancelsdescription
- Changed:get_app_statusOnly readsdescription
- Changed:remove_custom_domainDeletes or cancelsdescription
- Changed:set_forms_configDeletes or cancelsinputSchema
Tools5 changed.~5 changedView diff
- Changed:add_custom_domainChanges thingsdescription
- Changed:check_domain_availabilityChanges thingsdescription
- Changed:get_siteOnly readsdescription
- Changed:list_custom_domainsOnly readsdescription
- Changed:verify_custom_domainChanges thingsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcpclaude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vibedeploy__get_account",
"mcp__vibedeploy__list_sites",
"mcp__vibedeploy__get_site",
"mcp__vibedeploy__get_site_analytics",
"mcp__vibedeploy__read_file",
"mcp__vibedeploy__read_files",
"mcp__vibedeploy__list_file_hashes",
"mcp__vibedeploy__list_source_files",
"mcp__vibedeploy__read_source_file",
"mcp__vibedeploy__read_source_files",
"mcp__vibedeploy__search_files",
"mcp__vibedeploy__get_forms_config",
"mcp__vibedeploy__list_custom_domains",
"mcp__vibedeploy__list_dns_records",
"mcp__vibedeploy__list_deploys",
"mcp__vibedeploy__list_history",
"mcp__vibedeploy__list_snapshots",
"mcp__vibedeploy__get_app_status"
],
"ask": [
"mcp__vibedeploy__promote_dist_to_source",
"mcp__vibedeploy__verify_forms_sender_domain",
"mcp__vibedeploy__add_custom_domain",
"mcp__vibedeploy__verify_custom_domain",
"mcp__vibedeploy__check_domain_availability",
"mcp__vibedeploy__begin_deploy",
"mcp__vibedeploy__add_files",
"mcp__vibedeploy__add_file_chunk",
"mcp__vibedeploy__abort_deploy"
],
"deny": [
"mcp__vibedeploy__deploy_site",
"mcp__vibedeploy__update_site",
"mcp__vibedeploy__delete_site",
"mcp__vibedeploy__write_source_files",
"mcp__vibedeploy__delete_source_file",
"mcp__vibedeploy__build_and_deploy",
"mcp__vibedeploy__deploy_from_url",
"mcp__vibedeploy__rehost_images",
"mcp__vibedeploy__update_file_content",
"mcp__vibedeploy__apply_edits",
"mcp__vibedeploy__set_forms_config",
"mcp__vibedeploy__remove_custom_domain",
"mcp__vibedeploy__commit_deploy",
"mcp__vibedeploy__create_snapshot",
"mcp__vibedeploy__deploy_app",
"mcp__vibedeploy__remove_app"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vibedeploy. Review it before you use it.
Capability tags behind 36 rules
- mcp__vibedeploy__deploy_site untrusted-input
- mcp__vibedeploy__update_site untrusted-input
- mcp__vibedeploy__list_sites untrusted-input
- mcp__vibedeploy__get_site private-data, untrusted-input
- mcp__vibedeploy__delete_site untrusted-input
- mcp__vibedeploy__get_site_analytics untrusted-input
- mcp__vibedeploy__read_file private-data
- mcp__vibedeploy__read_files private-data
- mcp__vibedeploy__list_file_hashes private-data
- mcp__vibedeploy__list_source_files private-data
- mcp__vibedeploy__read_source_file private-data, untrusted-input
- mcp__vibedeploy__read_source_files private-data
- mcp__vibedeploy__write_source_files untrusted-input
- mcp__vibedeploy__build_and_deploy untrusted-input
- mcp__vibedeploy__search_files private-data
- mcp__vibedeploy__deploy_from_url untrusted-input
- mcp__vibedeploy__rehost_images untrusted-input
- mcp__vibedeploy__update_file_content untrusted-input
- mcp__vibedeploy__apply_edits untrusted-input
- mcp__vibedeploy__get_forms_config private-data, untrusted-input
- mcp__vibedeploy__verify_forms_sender_domain untrusted-input
- mcp__vibedeploy__add_custom_domain untrusted-input
- mcp__vibedeploy__verify_custom_domain untrusted-input
- mcp__vibedeploy__remove_custom_domain untrusted-input
- mcp__vibedeploy__list_custom_domains untrusted-input
- mcp__vibedeploy__check_domain_availability untrusted-input
- mcp__vibedeploy__begin_deploy untrusted-input
- mcp__vibedeploy__add_files untrusted-input
- mcp__vibedeploy__add_file_chunk untrusted-input
- mcp__vibedeploy__commit_deploy untrusted-input
- mcp__vibedeploy__abort_deploy untrusted-input
- mcp__vibedeploy__list_history private-data
- mcp__vibedeploy__list_snapshots private-data
- mcp__vibedeploy__create_snapshot untrusted-input
- mcp__vibedeploy__deploy_app untrusted-input
- mcp__vibedeploy__get_app_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/be.vibedeploy/vibedeploy/verify?hash=7f7c6c87654fe047ded7b70ba239a9f46342e2bae31276d618fee9c85c5fd27e" | jq -e '.changed == false'Pinned hash 7f7c6c87654f, from Nov 10, 2026, 07:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/be.vibedeploy/vibedeploy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/be.vibedeploy/vibedeploy)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:45 UTC.
VibeDeploy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VibeDeploy MCP server safe?
- No scan can promise that. What its definitions show: 43 tools, 25 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VibeDeploy MCP server delete data?
- Yes. 16 tools can delete, cancel or revoke something: deploy_site, update_site, delete_site, write_source_files, delete_source_file, build_and_deploy and 10 more.
Can the VibeDeploy MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: add_file_chunk.
What tools does the VibeDeploy MCP server have?
- 43 tools: 16 destructive, 1 irreversible, 8 write, 18 read. deploy_site, update_site, delete_site, write_source_files, delete_source_file, build_and_deploy, deploy_from_url, rehost_images and 35 more.
Does the VibeDeploy MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the VibeDeploy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the VibeDeploy MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.