Home / MCP registry index / cloud.dchub/mcp-server
DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber
cloud.dchub/mcp-server in the official MCP registry.
Endpoint https://dchub.cloud/mcp/registry. Source: github.com/azmartone67/dchub-mcp-server.
The registry describes it as: Data center energy, electricity & power grid data: DCPI to query and cite, capacity to buy or lease.
We read its 94 tools on 2026-10-25. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
claim_free_key search fetch execute_plan search_facilities get_facility get_market_intel get_market_dcpi_rank predict_market_trajectory get_gas_index get_gas_economics get_grid_scoreboard compare_isos get_intelligence_index list_transactions get_news semantic_search search_intelligence get_market_context get_iso_context get_pipeline get_power_pipeline get_infra_projects get_power_availability_timeline get_global_power get_interconnection_queue get_refined_queue get_retirement_headroom get_hosting_capacity analyze_parcel rank_sites discover_tools plan_query save_to_shortlist get_shortlist set_shortlist_alert suggest_reallocation get_grid_data get_changes get_facility_risk_delta save_site list_saved_sites set_market_alert subscribe_digest set_site_alert export_dataset find_sites analyze_site get_composite_site_score get_disaster_risk get_climate_intel generate_site_analysis compare_sites get_infrastructure get_fiber_intel get_fiber_readiness get_subsea_cables get_peering_intel get_metro_fiber get_energy_prices and 34 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/cloud-dchub-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.