Skip to main content
Glama
azmartone67

DC Hub Intelligence

by azmartone67
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Related Servers

Alternatives to DC Hub Intelligence

No user-submitted related servers found.

    Related Servers

    • GridWatch MCP

      mohithchow
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server exposing distributed industrial asset data (battery storage, EV chargers, solar arrays) with tools for asset status, geospatial search, alerts, anomaly explanation, and load simulation.
      734 npm
      MIT
    • kardashev-mcp by kardashev-lab

      kardashev-mcpofficial

      kardashev-lab
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Kardashev Labs US grid data, giving agents live LMP, carbon intensity, load, curtailment, interconnection queues, ERCOT large loads, and the public RT-DA spread forecast track record. Requires no API key.
      11
      37 npm
      MIT

    • worldmonitor-mcp

      mahimn01
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server wrapping worldmonitor global intelligence dashboard, exposing 140 tools across 32 services for live market, geopolitical, military, cyber, climate, and supply chain data.
      MIT

    • aemo-mcp

      Bigred97
      A
      license
      A
      quality
      B
      maintenance
      One-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.
      5
      129 PyPI
      MIT

    • SEC EDGAR Data MCP

      SEC-API-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Hosted MCP server granting AI agents access to 20M+ SEC EDGAR filings, 100M+ exhibits, and comprehensive entity data through 49 tools, with support for raw documents, extracted sections, and structured JSON.
      13 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 92 tools

    Disambiguation3/5

    Many tools target closely related outcomes (e.g., analyze_site vs get_composite_site_score vs score_facility for site scoring; get_grid_intelligence vs get_grid_data vs get_iso_context vs get_grid_scoreboard for grid data). Descriptions do include explicit 'Do NOT use' guidance, but the sheer number of overlapping read paths creates real misselection risk.

    Naming Consistency4/5

    Tool names are overwhelmingly snake_case and often follow a verb_noun pattern (get_grid_intelligence, rank_markets, save_site). A few noun-phrase deviations exist (ai_capacity_index, deal_autopsy, why_dchub, site_selection_canvas), but the convention remains predictable and readable.

    Tool Count1/5

    92 tools is an extreme mismatch for a typical MCP surface. Even a broad data-center and energy intelligence domain does not justify this many separate tools when many are narrow variations on the same read.

    Completeness5/5

    The surface covers an exceptionally wide domain: facilities, markets, grid, gas, fiber, peering, water, climate, disaster risk, permits, tax incentives, deals, news, capacity sourcing, and account/alert management. No obvious lifecycle or intelligence gaps stand out for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources