MCP servers observed by Lowdown
be.vibedeploy/vibedeploy MCP server: daily status and tool changes
Answered initialize and tools/list on all 30 daily checks recorded in the last 30 days (2026-10-20 to 2026-11-18); 43 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:be.vibedeploy/vibedeploy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:be.vibedeploy/vibedeploy?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 30
- Answered initialize and tools/list: 30
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 6 of 30 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed
- 2026-11-10: input or output schemas changed
- 2026-11-07: descriptions changed
- 2026-11-04: descriptions changed
- 2026-10-23: input or output schemas changed
What tools does it list?
43 tools on 2026-11-18:
abort_deployadd_custom_domainadd_file_chunkadd_filesapply_editsbegin_deploybuild_and_deploycheck_domain_availabilitycommit_deploycreate_snapshotdelete_sitedelete_source_filedeploy_appdeploy_from_urldeploy_siteget_accountget_app_statusget_forms_configget_siteget_site_analyticslist_custom_domainslist_deployslist_dns_recordslist_file_hasheslist_historylist_siteslist_snapshotslist_source_filespromote_dist_to_sourceread_fileread_filesread_source_fileread_source_filesrehost_imagesremove_appremove_custom_domainsearch_filesset_forms_configupdate_file_contentupdate_siteverify_custom_domainverify_forms_sender_domainwrite_source_files
MCP Registry declaration
- Registry name:
be.vibedeploy/vibedeploy - Declared version: 1.1.0
- Status: active
- Declared hosts:
mcp.vibedeploy.be
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:be.vibedeploy/vibedeploy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:be.vibedeploy/vibedeploy?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).