MCP servers observed by Lowdown
cloud.redu/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 119 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-12 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:cloud.redu/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.redu/mcp?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: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-12: input or output schemas changed, descriptions changed, tool names changed; tool count 113 → 119
What tools does it list?
119 tools on 2026-11-18:
add_security_group_rulearchitecture_diagramattach_volumecheck_deploy_prerequisitescheckpoint_runcreate_api_keycreate_backupcreate_clickhousecreate_databasecreate_free_postgrescreate_free_websitecreate_instancecreate_media_spacecreate_private_networkcreate_private_vpscreate_qdrantcreate_rediscreate_relational_databasecreate_runcreate_run_keycreate_security_groupcreate_snapshotcreate_volumedelete_api_keydelete_backupdelete_clickhousedelete_clusterdelete_databasedelete_deploymentdelete_dns_entrydelete_free_resourcedelete_instancedelete_keypairdelete_private_networkdelete_private_vpsdelete_qdrantdelete_redisdelete_relational_databasedelete_security_groupdelete_security_group_ruledelete_snapshotdelete_volumedeploy_appdeploy_composedeploy_overviewdeploy_vpndetach_volumeend_runexec_free_resourceexec_private_vpsget_billing_accountget_container_logsget_containersget_deploymentget_domain_verificationget_env_keysget_free_resource_actionget_free_resource_telemetryget_free_resourcesget_free_website_sshget_instance_logsget_private_vps_actionget_private_vps_pilotget_private_vps_sshget_resource_usageget_runget_ssh_commandimport_keypairinstance_actionintegrate_overviewlist_api_keyslist_backupslist_clickhouse_databaseslist_clusterslist_databaseslist_deploymentslist_dns_entrieslist_domainslist_flavorslist_imageslist_instanceslist_keypairslist_media_spaceslist_private_networkslist_qdrantlist_redislist_regionslist_relational_databaseslist_runslist_security_groupslist_snapshotslist_volumespause_runplan_deployplan_instanceplan_managed_datastorepostgres_data_changepostgres_data_readprepare_uploadpublish_free_websitepublish_private_vpsrelease_domainrenew_runrestore_backuprestore_runresume_runscaffold_localselect_surfaceset_cluster_domainset_instance_security_groupsset_managed_backupsupdate_clusterupdate_security_groupupgrade_to_clusterupgrade_to_haverify_deploymentverify_domainwait_for_deploymentwhoami
MCP Registry declaration
- Registry name:
cloud.redu/mcp - Declared version: 0.1.1
- Status: active
- Declared hosts:
mcp.redu.cloud
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:cloud.redu/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.redu/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).