MCP servers observed by Lowdown
de.run-zero/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 53 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 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:de.run-zero/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:de.run-zero/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 51 → 53
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 50 → 51
What tools does it list?
53 tools on 2026-11-16:
runzero_activate_versionrunzero_add_servicerunzero_adopt_templaterunzero_backup_volumerunzero_claim_handoffrunzero_create_apprunzero_create_identity_providerrunzero_create_userrunzero_db_queryrunzero_delete_apprunzero_delete_secretrunzero_delete_servicerunzero_delete_userrunzero_deployrunzero_deploy_previewrunzero_describe_addonrunzero_generate_imagerunzero_get_apprunzero_get_build_logsrunzero_get_helprunzero_get_legal_profilerunzero_get_logsrunzero_get_metricsrunzero_import_volumerunzero_list_appsrunzero_list_buildsrunzero_list_filesrunzero_list_identity_providersrunzero_list_releasesrunzero_list_secretsrunzero_list_servicesrunzero_list_templatesrunzero_list_usersrunzero_list_versionsrunzero_preview_versionrunzero_publishrunzero_push_filesrunzero_read_filerunzero_rebuild_servicerunzero_reset_user_passwordrunzero_restore_releaserunzero_restore_volumerunzero_scale_servicerunzero_screenshotrunzero_set_legal_profilerunzero_set_publish_moderunzero_set_secretsrunzero_set_user_enabledrunzero_upload_assetsrunzero_volume_import_linkrunzero_volume_statusrunzero_wait_for_buildrunzero_work_url
MCP Registry declaration
- Registry name:
de.run-zero/mcp - Declared version: 1.0.2
- Status: active
- Declared hosts:
api.run-zero.de
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:de.run-zero/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:de.run-zero/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).