MCP servers observed by Lowdown
cloud.dchub/mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on the last 3 consecutive daily checks (2026-11-16 to 2026-11-18); 97 tools listed. 3 of 24 observed days in the last 30 had this result. On 2026-11-17 a tool description with a URL appeared. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-26; tool definitions change on most observed days (14 of 23); 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.dchub/mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.dchub/mcp-server?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: 24
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 21
Does it require authentication?
It did not return HTTP 401/403 on any of the 24 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 14 of 23 compared days. Changes are routine for this server, so a single change says little on its own.
- 2026-11-18: input or output schemas changed
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 96 → 97; a tool description with a URL appeared
- 2026-11-16: input or output schemas changed, descriptions changed, server version changed
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 95 → 96
- 2026-11-15: server version changed
What tools does it list?
97 tools on 2026-11-18:
accept_capacity_termsai_capacity_indexanalyze_parcelanalyze_sitebind_emailclaim_free_keycluster_sites_by_latencycompare_isoscompare_sitesdchub_servicesdeal_autopsydelete_standing_intentdiscover_toolsexecute_planexport_datasetfetchfind_alternativesfind_sitesgenerate_site_analysisget_agent_registryget_air_permit_contextget_backup_statusget_changesget_climate_intelget_composite_site_scoreget_dchub_recommendationget_disaster_riskget_energy_pricesget_facilityget_facility_risk_deltaget_fiber_intelget_fiber_readinessget_gas_economicsget_gas_indexget_gas_intelligenceget_global_powerget_grid_dataget_grid_intelligenceget_grid_scoreboardget_hosting_capacityget_infra_projectsget_infrastructureget_intelligence_indexget_interconnection_queueget_iso_contextget_market_contextget_market_dcpi_rankget_market_intelget_metro_fiberget_newsget_peering_intelget_permitting_intelget_pipelineget_power_availability_timelineget_power_pipelineget_refined_queueget_renewable_energyget_retirement_headroomget_shortlistget_subsea_cablesget_tax_incentivesget_water_riskgrid_transition_radarhyperscaler_dealslist_saved_siteslist_standing_intentslist_transactionsplan_fiber_leadinplan_querypredict_market_trajectoryrank_marketsrank_sitesread_inboxrecover_my_keyregister_standing_intentreport_findingrequest_capacity_introrequest_enhancementresearch_tasksave_sitesave_to_shortlistscore_facilitysearchsearch_facilitiessearch_intelligencesemantic_searchset_market_alertset_shortlist_alertset_site_alertsimulate_scenariosite_selection_canvassource_capacitysubscribe_digestsuggest_reallocationsummarize_for_citationunlock_more_datawhy_dchub
MCP Registry declaration
- Registry name:
cloud.dchub/mcp-server - Declared version: 2.12.59
- Status: active
- Declared hosts:
dchub.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.dchub/mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.dchub/mcp-server?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:cloud.dchub/mcp-server -- npx -y dchub-mcp-server
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).