MCP servers observed by Lowdown
net.bot-hosting/mcp MCP server: daily status and tool changes
Required authentication (HTTP 401/403) on the last 2 consecutive checks (2026-11-15 to 2026-11-18) (Lowdown checks this server every 3 days). Lowdown checks without credentials, so no tools were listed. 2 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-12; 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:net.bot-hosting/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.bot-hosting/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server required authentication (HTTP 401/403).
- Observed days in the last 30: 3
- Answered initialize and tools/list: 1
- Required authentication: 2
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 2 of 3 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
72 tools on 2026-11-12:
account_getbackups_getbackups_listbackups_restoredatabases_rotatePassworddeployments_applydeployments_checkdeployments_commanddeployments_createdeployments_deletedeployments_diagnosedeployments_enableDomainsdeployments_getdeployments_getGitdeployments_getStartupdeployments_listdeployments_logsdeployments_movedeployments_powerdeployments_removeCustomDomaindeployments_removeSlugdeployments_resizedeployments_resourcesdeployments_searchLogsdeployments_setAutoPulldeployments_setCustomDomaindeployments_setSlugdeployments_sftpdeployments_shelldeployments_syncdeployments_updatedeployments_updateStartupdeployments_verifyCustomDomaindocs_getdocs_searchenv_auditenv_deleteenv_listenv_setenv_updatefiles_chmodfiles_compressfiles_copyfiles_decompressfiles_deletefiles_downloadUrlfiles_editfiles_editManyfiles_historyfiles_indexfiles_listfiles_mkdirfiles_movefiles_outlinefiles_readfiles_readManyfiles_renamefiles_restorefiles_searchfiles_treefiles_uploadUrlfiles_writefiles_writeManypackages_addpackages_listpackages_removeprojects_createprojects_deleteprojects_listruntimes_listtemplates_gettemplates_list
MCP Registry declaration
- Registry name:
net.bot-hosting/mcp - Declared version: 1.0.0
- Status: active
- Declared hosts:
bot-hosting.net
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:net.bot-hosting/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.bot-hosting/mcp?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).