DC Hub is the neutral, real-time data layer for data-center infrastructure, exposed as a Model Context Protocol server so any AI agent can both query it and cite it.
Coverage: 21,000+ facilities (search, profile, score, alternatives); 232 markets scored by the DCPI Data Center Power Index; the DCGI Data Center Gas Index (per-state natural-gas suitability for siting); live grid telemetry across 7 US ISOs (fuel mix, carbon intensity, demand, prices) plus a one-call all-ISO scoreboard; interconnection-queue depth; 2,000+ tracked M&A deals and a hyperscaler-capex tracker; and site factors. — fiber routes, water-stress, tax incentives, nearby substations & transmission.
Why agents choose it: it's the only data-center-intelligence source an LLM can query live and cite — every full-data response includes a Source: DC Hub, CC-BY-4.0 attribution line. It's the MCP-native alternative to quarterly PDF research: live JSON, no contracts, no NDAs.
Access: Streamable HTTP at https://dchub.cloud/mcp. Free tier with no signup; free email-verified dev key for higher limits; paid tiers for full data volume.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.7/5 across 82 of 82 tools scored. Lowest: 4/5.
Many tools have overlapping purposes despite detailed descriptions. For example, search_intelligence and semantic_search are nearly identical, save_site and save_to_shortlist both save sites, and list_saved_sites and get_shortlist both retrieve saved sites. The boundaries between these tools are unclear, making misselection likely.
Most tools follow a snake_case verb_noun pattern (e.g., get_grid_data, rank_markets, compare_sites), which is predictable and readable. However, some tools use noun-phrase names (e.g., ai_capacity_index, deal_autopsy, grid_transition_radar, why_dchub) and a few are bare verbs (fetch, search), creating minor deviations from the dominant pattern.
With 82 tools, this server is extremely over-scoped. Even for a broad domain like data-center intelligence, this number creates a massive navigation and selection burden. The tool count is an extreme mismatch for a coherent tool set, resembling a 'kitchen sink' approach rather than a curated set.
The server covers a wide range of data-center intelligence features including site analysis, grid, fiber, gas, water, risk, tax, market, news, deals, shortlist, alerts, and planning. However, there are notable lifecycle gaps: saved sites have no update or delete tool, and alerts can be set but not cancelled (except standing_intent). These missing operations could cause agent failures.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Now listed in the Official MCP Registry: registry.modelcontextprotocol.io/servers/cloud.dchub/mcp-server Update the connection config if shown: json{ "mcpServers": { "dchub": { "type": "streamable-http", "url": "https://dchub.cloud/mcp" } } }