{"data":{"name":"cloud.dchub/mcp-server","title":"DC Hub","description":"Orchestration layer for data center and energy intelligence. Start with execute_plan.","version":"2.12.59","websiteUrl":"https://dchub.cloud","repositoryUrl":"https://github.com/azmartone67/dchub-mcp-server","remotes":[{"type":"streamable-http","url":"https://dchub.cloud/mcp"}],"packages":[{"registryType":"npm","identifier":"dchub-mcp-server","version":"2.12.59","runtimeHint":"stdio","runtimeArguments":null,"environmentVariables":null}],"status":"active","isLatest":true,"publishedAt":"2026-11-16T09:04:01.871Z","updatedAt":"2026-11-16T09:04:01.871Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"source":"official-registry","sourceId":"cloud.dchub/mcp-server","verification":"official","confidence":100,"stars":null,"updatedAt":"2026-11-16T09:04:01.871Z","title":"DC Hub","description":"Orchestration layer for data center and energy intelligence. Start with execute_plan.","websiteUrl":"https://dchub.cloud","repositoryUrl":"https://github.com/azmartone67/dchub-mcp-server"}],"toolIndex":{"tools":[{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"analyze_parcel","title":"Analyze Parcel","description":"Use this when the user has a land parcel for a data center site: structured read of its boundary — pass your own GeoJSON Polygon/MultiPolygon, OR just lat+lon and DC Hub finds the containing parcel in its HOSTED parcel-boundary layer (free county/state GIS polygons, covering a set of priority data-center counties in VA, IL, TX, OH, UT, OR, IA and WY; a point outside it returns parcel_not_covered with the analyze_site preview + the coverage list, never a guess). Returns _entity=parcel_analysis: geodesic total_acres, a per-member acreage breakdown, a contiguous flag, representative_point = the centroid of the LARGEST-area member (never the multi-part geometric center, which can land off-parcel on a highway median or river and poison every point-keyed read), and hosted_parcel {parcel_id, county, state, acres_per_source} when the polygon came from the hosted layer. Also returns a site_evaluation_handoff to pipe into analyze_site + get_water_risk at that anchor. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"geometry":{"description":"GeoJSON Polygon or MultiPolygon parcel boundary, e.g. {\"type\":\"Polygon\",\"coordinates\":[[[lng,lat],[lng,lat],...]]} — a MultiPolygon carries discontinuous parcels as one envelope. Omit to look up the hosted parcel containing lat/lon instead"},"lat":{"description":"Latitude of a point ON the parcel — used with lon when geometry is omitted to look up the containing parcel from the hosted county/state GIS layer","type":"number"},"lon":{"description":"Longitude of a point ON the parcel (used with lat when geometry is omitted)","type":"number"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"},"capacity_mw":{"description":"Optional target load in MW to pass through into the site_evaluation_handoff","type":"number"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"f1551b0bb76aab84f6968652eec5152870fc15e96855bb054ff88433d8b6a102","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"analyze_site","title":"Analyze Site","description":"Use this when the user asks whether a specific site or coordinate works for a data center (lat/lon, or a market name for a market-level read). Returns a 0-100 composite, verdict, power/gas/fiber/market/risk sub-scores, nearby infrastructure and power cost; capacity_mw adds a capacity_context block and does NOT move overall_score. Keyless returns the verdict band and the power band, with the other factors named; a free key adds a few free full site reports each month; other scores and figures need a paid DC Hub plan. When a result is partial, show your user the human_message (or for_your_human) text and its link. Ex: \"Score 33.45,-112.07 for 100 MW.\" Next: to buy or lease capacity in these markets, call source_capacity; to register a requirement with providers, call request_capacity_intro after your human approves. Needs BOTH lat and lon in decimal degrees (else missing_coordinates); take them from get_facility or search_facilities. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"candidate_id":{"description":"PREFERRED for queue survivors: a cand_… id from get_refined_queue — coordinates come from the FROZEN mint (lat/lon args are ignored; zero transcription drift; expired ids fail closed with candidate_expired).","type":"string"},"lat":{"description":"Site latitude in decimal degrees (-90 to 90; required unless candidate_id or location given), e.g. 33.45","type":"number"},"lon":{"description":"Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07","type":"number"},"location":{"description":"Market NAME or metro slug instead of coordinates, e.g. \"ashburn\", \"northern-virginia\", \"dallas\". Resolved to that market's PUBLISHED CENTROID through the DCPI market row, and the answer carries a resolved_from block saying so.","type":"string"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"},"state":{"description":"US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ","type":"string"},"capacity_mw":{"description":"Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500)","type":"number"},"include_grid":{"description":"Include grid-headroom / substation analysis (default true)","type":"boolean"},"include_risk":{"description":"Include water/drought/climate risk analysis (default true)","type":"boolean"},"include_fiber":{"description":"Include fiber-connectivity analysis (default true)","type":"boolean"},"mpp_pay":{"description":"Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.","type":"boolean"},"mpp_credential":{"description":"Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"6c77e7008b088cf4ec4bfd27ecfeddcb14c3a4ce3bffc22f7a6a27558b124336","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"claim_free_key","title":"Claim Free Key","description":"Use this when the user wants more DC Hub data center data than keyless allows, or asks for a key; no key is needed to start. Mints a free key and returns it plus connect_url, a connector URL with the key embedded (the only thing hosted chat clients keep). Free key: previews plus 2 full answers per tool per day. WHAT AN EMAIL GETS (free, no card): 50 calls/day (up to 10 full answers per tool per day); 10 full answers a day each on the grid, queue and market-intel tools instead of previews; a weekly summary of what your key looked up (unsubscribe anytime); a key that can be recovered (recover_my_key re-sends it to that inbox). Ask the user for an email first; pass it only if they typed it. Save and reuse the key (lost one: recover_my_key); don't re-mint. Then ask the real question (execute_plan for multi-step). If a call was answered with a sign-in challenge (401 WWW-Authenticate), prefer signing in: that identity persists, but a human must finish it in a browser. No challenge (Claude Code, Cursor, most agents) means OAuth is not available to you and the key is right. Ex: \"Set me up with a DC Hub key.\" For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"client_name":{"description":"Your agent/app name for attribution, e.g. \"Claude Desktop\" or \"acme-siting-bot\"","type":"string"},"email":{"description":"Optional owner email to make the key recoverable across sessions; use only an address your human explicitly gave","type":"string"}}},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false},"definitionHash":"7dd3228ea58ca73be4cb2cea5fd5c0e1ce4a06eaa11bbc15a74443f3501c07b1","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"compare_isos","title":"Compare ISO Regions","description":"Use this when the user asks to compare two to four power grids side by side — fuel mix, demand, renewable/gas share, and for the US ISOs interconnection-queue depth and time-to-power — in one call instead of N sequential get_grid_intelligence calls. Example: \"Compare PJM vs ERCOT vs CAISO on gas share, renewable share, and queue depth right now.\" — compare_isos isos=\"PJM,ERCOT,CAISO\"; \"ERCOT vs AESO vs EU_DE_LU\" also works. Params: isos is a comma-separated list (2-4 max): any of the 7 US ISOs (\"PJM\" | \"ERCOT\" | \"CAISO\" | \"MISO\" | \"SPP\" | \"NYISO\" | \"ISO-NE\"), TVA, BPA, a US utility BA, or a non-US grid (IESO, AESO, HYDROQUEBEC, NGESO, EU_<zone>, TAIPOWER, OCCTO, KEPCO-KR, ONS, AEMO, EMA); non-US and non-ISO rows carry null DCPI and queue fields (not tracked, not zero). Returns: {isos[], comparison:{<iso>:{demand_mw, generation_mix_pct, renewable_share_pct, gas_share_pct, constraint_score, excess_power_score, avg_time_to_power_months, avg_queue_wait_months, queue_depth_gw, retail_price_cents_kwh}}, as_of}. ★avg_time_to_power_months (DCPI per-market estimate, ISO-averaged) and avg_queue_wait_months (proxy from live queue DEPTH) are DIFFERENT measurements — quote whichever you mean by name. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"isos":{"type":"string","description":"Comma-separated list of 2-4 grids to compare, e.g. \"PJM,ERCOT,CAISO\" or \"ERCOT,AESO,EU_DE_LU\": US ISOs (ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE), TVA, BPA, utility BAs, or non-US grids (IESO, AESO, HYDROQUEBEC, NGESO, EU_<zone>,…"}},"required":["isos"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"f6744ab72fcb8e4e6bef4884c970259ad8229369092a435793feb4d6fbd9b9ce","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"discover_tools","title":"Discover Tools","description":"Use this when you are unsure which DC Hub data center, power or grid tool fits: lists tools by family. Returns _entity=tool_families — a front_door block (execute_plan for any multi-capability question, get_changes to refresh) plus families with a when-to-use note + their tools (facility, market, grid_power, gas_btm, site_geometry, fiber, deals_news, saved_work, account_meta, partner), optionally filtered by a query. Then call the chosen tool (its full schema is in tools/list). This is a navigation layer, not the exhaustive catalog — tools/list stays canonical, and if you are BINDING a capability map, bind it from tools/list, not from here. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"query":{"description":"Optional keyword to filter families/tools, e.g. \"site selection\", \"grid queue\", \"fiber\", \"deals\", \"market\"","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"68aef9d3e3a985f584b39e4c8133792eeba8ee13030a9cdf32187819f08400e8","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"execute_plan","title":"Execute Plan","description":"Use this when a data center question spans several topics: one-call planner over grid headroom and power availability, interconnection queues, PPAs and energy pricing, power generation, gas and energy infrastructure (the Data Center Gas Index, DCGI), substations and transmission, megawatts and power density, site selection and buildable capacity, colocation and wholesale data-center markets, AI/GPU compute campuses, fiber routes, diversity and latency, tax incentives and permitting, water and climate risk, data-center M&A and deals. Recommended entry for a question that spans more than one of those: it picks and chains the right tools and returns one dated, cited answer. Pass the user's question as `intent`. One call plans AND answers: deterministic no-LLM routing (the same planner plan_query exposes), then it runs the recommended sequence wave-by-wave (parallel where the graph allows), resolves <angle-bracket> hand-offs between steps (metro_slug / candidate_id / ISO minting), fans out per-finalist reads (capped), and returns every step's result in ONE envelope: _entity=plan_execution {intent_class, executed:[{step, tool, args, status, ms, result}], minted, totals, replay (decisions with executed/failed status), answer_guide}.","inputSchema":{"type":"object","properties":{"intent":{"type":"string","description":"The user's infrastructure question, passed through UNCHANGED. Examples: \"how soon can a 100 MW load get power in ERCOT\" · \"evaluate 100 MW power headroom for a GPU training cluster in PJM\" · \"interconnection queue and energy prices in MISO…"},"context":{"description":"Optional structured hints AND step-arg overrides: {lat, lon, iso, market, capacity_mw, candidate_id, state, since} — user-supplied values beat minted ones. The typed top-level params below are merged into this and WIN on conflict."},"market":{"description":"Metro slug or name to pin the analysis to, e.g. \"ashburn\". Beats any market the planner would mint.","type":"string"},"capacity_mw":{"description":"Target capacity in MW, e.g. 100.","type":"number"},"iso":{"description":"ISO/RTO code to pin geography, e.g. \"PJM\", \"ERCOT\".","type":"string"},"state":{"description":"US state code, e.g. \"VA\".","type":"string"},"lat":{"description":"Latitude for a specific site.","type":"number"},"lon":{"description":"Longitude for a specific site.","type":"number"},"max_steps":{"description":"Max plan steps to execute, 1-8 (default 6)"},"max_fanout":{"description":"Max per-finalist fan-out calls for one step, 1-3 (default 2)"},"cohort":{"description":"Optional experiment tag for adoption/retention measurement, e.g. \"cohort.front_door\". Has NO effect on routing, planning, geography or results — it is recorded only."}},"required":["intent"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"e9857f5f3be92b61fb60dd00d767ed64736c355850e32667793f2fa159ee1de5","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"export_dataset","title":"Export Dataset","description":"Use this when the user wants to export their saved data center sites for offline analysis, a spreadsheet, or ingestion into another tool (paid plan). Example: \"Export my saved sites as GeoJSON for QGIS.\" — export_dataset format=geojson. Params: format (\"csv\" default, or \"geojson\"). Returns: the full file contents as text — CSV rows or a GeoJSON FeatureCollection of your saved sites with DCPI score, target MW, market, coordinates, and notes. Do NOT use to list sites in-chat (use list_saved_sites) or to save a new one (use save_site); this is the bulk-download path. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"format":{"description":"Output file format: \"csv\" (default) or \"geojson\" (for GIS tools like QGIS)","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"3bbb619a0f435b81687d071ad8fc4624de4fcce9cad1d04ea8c30981d6eb8859","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"fetch","title":"Fetch","description":"Use this when you have an id from `search` and need that data center facility record (search/fetch format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, status, market). For full structured specs (capacity MW, coordinates) use get_facility or open the url. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"id":{"type":"string","description":"A facility id/slug from a prior `search` result, e.g. equinix-dc1-ashburn"}},"required":["id"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"5f4f01e2a22a3011283acd115b099896198dfc54758adc0649d28fbd5b1db80a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"find_sites","title":"Find Sites","description":"Use this when the user has no data center site yet and wants candidate search areas (site selection by substation voltage, gas and fiber distance); execute_plan covers a multi-part siting question. THE INVERSE QUERY: every other DC Hub siting tool needs a coordinate you already have — analyze_site scores one, get_composite_site_score grades one, rank_sites orders candidates YOU already enriched, find_alternatives needs a seed facility. This one answers \"where should I even be looking?\". Returns candidate SEARCH AREAS anchored on real HIFLD substations at or above min_voltage_kv, spatially de-duplicated by cluster_km so a dense metro yields distinct areas instead of 40 near-identical rows, each carrying measured distance to the nearest gas pipeline and fiber route plus state-grain moratorium context, and a next_calls handoff. Answers \"where should I even be looking for 200 MW in Ohio\" and \"which areas near Dallas sit on 230kV with gas within 5 miles\". Try: find_sites state=OH min_voltage_kv=230 max_gas_km=8 — or find_sites lat=39.04 lon=-77.48 radius_km=60 min_voltage_kv=500. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"state":{"description":"2-letter US state to search, e.g. OH — required unless you pass lat + lon","type":"string"},"lat":{"description":"Latitude of a search centre, e.g. 39.04 — use with lon (+ radius_km) instead of state","type":"number"},"lon":{"description":"Longitude of a search centre, e.g. -77.48","type":"number"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"},"radius_km":{"description":"Search radius in km around lat/lon (default 80, clamped 5-400); ignored in state mode","type":"number"},"min_voltage_kv":{"description":"Only anchor on substations at or above this voltage in kV (default 115). 230+ for hyperscale, 500 for the largest campuses","type":"number"},"max_gas_km":{"description":"Drop candidates farther than this from the nearest gas pipeline. Applied ONLY if the gas layer answers — check constraint_coverage","type":"number"},"max_fiber_km":{"description":"Drop candidates farther than this from the nearest fiber route (CHORD approximation — see fiber_distance_basis). Applied ONLY if the fiber layer answers","type":"number"},"exclude_moratorium":{"description":"true = drop candidates in a state with a published data-center moratorium. STATE grain, not jurisdiction grain","type":"boolean"},"cluster_km":{"description":"Collapse anchors within this many km into one candidate area (default 8, max 100). Raise it for broader coverage, lower it for denser results","type":"number"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"eb42932cd3b5155c1797e57ac667b840e11508800287adb291a80909139d7287","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_changes","title":"Get Changes","description":"Use this when the user asks what changed in data center markets, facilities or deals since a date. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed callers with saved sites, a `portfolio` block answering \"did MY sites move?\": per-saved-site verdict flips (CAUTION → BUILD), excess-power deltas, alerts fired, and new facilities near each site since your last check. Pass since=<ISO-8601> or shorthand \"24h\"/\"7d\" (default 24h); cache the response generated_at and pass it back next call. Answers \"what changed since I last looked\", \"anything new this week I should know about\". Try: get_changes since=7d. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"since":{"description":"Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand \"24h\"/\"7d\"; default 24h","type":"string"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e0ede2de469166daabc88f4d0dcd246250019cdb82c684c70850269ea6e5f5f4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_composite_site_score","title":"Get Composite Site Score","description":"Use this when the user wants one 0-100 data center site suitability verdict for a lat/lon WITH an explicit per-factor coverage map — which factors are actually measured vs. declared unavailable. Unlike analyze_site (full raw data dump), this scores ONLY over VALIDATED factors and never imputes a missing one: power/grid, fiber, natural-hazard risk (FEMA NRI) and water (live WRI Aqueduct 4.0 baseline water stress) are all live; water is \"unavailable\" only outside basin coverage (never faked); market/DCPI is v1-unavailable (use rank_markets). Example: get_composite_site_score lat=33.45 lon=-112.07 state=AZ. Returns {composite_score (0-100 over validated factors), verdict (BUILD/CAUTION/AVOID), confidence (complete|conditional), coverage {power_grid|fiber|water|risk_resilience|market_dcpi: validated|unavailable}, coverage_ratio, sub_scores, caveats}. Use analyze_site for full data, compare_sites for 2-4 sites, rank_markets for whole-market ranking. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"lat":{"description":"Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45","type":"number"},"lon":{"description":"Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07","type":"number"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"},"state":{"description":"US state abbreviation (optional) — improves water/context lookups, e.g. AZ","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"8a12bed3e5e63b78480a081cfe6eee5acf963f02ca707b9d986b8ee6e0df2219","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_disaster_risk","title":"Get Disaster Risk","description":"Use this when the user asks about natural-hazard risk for a data center site (US lat/lon) — flood, wildfire, hurricane, earthquake, heat, drought, tornado, etc. Grounded in the FEMA National Risk Index (NRI), the US county-level hazard dataset (live query, never estimated; points outside US NRI coverage return coverage=unavailable). Example: get_disaster_risk lat=33.45 lon=-112.07. Returns {disaster_risk:{composite_score (0-100, higher=worse), rating (Very Low..Very High), national_percentile}, hazards:{Wildfire, Hurricane, Earthquake, Heat Wave, ...: rating}, top_hazards:[{hazard, rating}], coverage (validated|unavailable), source, caveats}. County-level resolution. For chronic water stress use get_water_risk; for one blended site verdict use get_composite_site_score. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"lat":{"description":"Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45","type":"number"},"lon":{"description":"Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07","type":"number"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"f97794b590271a77c3041e30528c111feacfa8e61fd43cbb917e1daf7395c288","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_facility","title":"Get Facility Details","description":"Use this when the user asks about one data center facility: name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby. Answers \"who operates this data center and how big is it\", \"how many fiber carriers are in that building\". Try: get_facility id=equinix-dc1-ashburn — or get_facility slug=digital-realty-digital-realty-iad38-ashburn-5754e62d. Returns ONE facility in full; do NOT use to search or list many facilities (use search_facilities). Needs a slug or id from search_facilities. 404 \"not found\": re-run search_facilities. Gated: give human_url to your human. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"facility_id":{"description":"Facility id from a prior search_facilities/search result (numeric or string), e.g. equinix-dc1-ashburn","anyOf":[{"type":"string"},{"type":"number"}]},"slug":{"description":"Facility slug from a prior search result, e.g. digital-realty-digital-realty-iad38-ashburn-5754e62d","type":"string"},"id":{"description":"Alias for facility_id — a facility id/slug from a prior search result","anyOf":[{"type":"string"},{"type":"number"}]},"name":{"description":"Facility name as a fallback lookup when no id/slug is known, e.g. \"QTS Ashburn\"","type":"string"},"include_nearby":{"description":"Include peer facilities near this one in the response (default true)","type":"boolean"},"include_power":{"description":"Include power capacity detail (total/used MW) in the response (default true)","type":"boolean"}},"anyOf":[{"properties":{"facility_id":{}},"required":["facility_id"]},{"properties":{"id":{}},"required":["id"]},{"properties":{"slug":{}},"required":["slug"]},{"properties":{"name":{}},"required":["name"]}]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"8dd6c7b1621b986c012750ba921374e8ddd4e055ae4ca3e5464b21402763fdde","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_facility_risk_delta","title":"Get Facility Risk Delta","description":"Use this when the user asks how a data center facility's (or its market's) power risk changed recently — \"has this site gotten riskier lately?\". Returns the REAL DCPI market-health delta (excess-power score change over the window, direction improving/worsening/flat) from DC Hub's history-preserving daily snapshots. INTEGRITY: only DCPI market-health has a short-term temporal series; the site-hazard dimensions (FEMA disaster / USGS seismic / NOAA climate / WRI water) are DECLARED static (they don't change week-to-week) with a pointer to the point-in-time tool — never a fabricated week-over-week delta; no snapshot history → coverage:unavailable. Params: facility_id (a discovered-facility id or slug) OR market (a market name/slug), since (e.g. \"7d\"/\"30d\", default 7d). Returns {facility, dcpi_market_health:{delta, now, direction, coverage}, static_dimensions{...}, summary}. For the current point-in-time risk (not the change) use get_composite_site_score / get_disaster_risk / get_climate_intel. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"facility_id":{"description":"A DC Hub facility id or canonical slug to resolve the market context","type":"string"},"market":{"description":"Alternatively, a market name or slug (e.g. \"northern-virginia\")","type":"string"},"since":{"description":"Look-back window, e.g. \"7d\" or \"30d\" (default 7d)","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"9b1fd5696130cc7b070db37d7bfbf65fb7f53105649d8486c2daf680f68a2a26","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_gas_economics","title":"Get Gas Economics","description":"Use this when the user asks what behind-the-meter gas power costs in a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market=<slug> (e.g. \"northern-virginia\", \"dallas\", \"phoenix\"). AZ, GA, FL), never a substitute price; if the backend switch is ever turned off again, `gas_to_grid_status` carries that reason. ★ DO NOT COMPARE a $/MWh published before 2026-09-27 with one published now — each surface then picked the price its own way, up to 5.5x apart. Do not derive a $/MWh yourself from the $/MMBtu layers for a withheld state without saying that you did. Do NOT use for the electricity grid fuel mix (use get_grid_data). For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"market":{"type":"string","description":"Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank"},"heat_rate_btu_per_kwh":{"description":"Optional custom generator heat rate in Btu/kWh for the gas-to-grid $/MWh scenario, e.g. 6800 (avg CCGT)","type":"number"}},"required":["market"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"752a43ea4c929345681f9e442a356aac467cb2ad42b0cd06714f0fe8c1808d04","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_gas_index","title":"Gas Index (DCGI)","description":"Use this when the user asks which US states suit gas-fired data center power: the Data Center Gas Index (DCGI), a per-state score. ★ DO NOT COMPARE a DCGI figure published before 2026-08-08 with one published now — they are different indices; the full record is at /api/v1/dcgi/methodology under `corrections`. A state that cannot be priced comes back verdict UNSCORED with dcgi null and an `unscored_reason`, never a placeholder score, so treat UNSCORED as absence and not as a low score. `gas_price_series` names which EIA series answered each state. Gas-fired $/MWh figures, withdrawn the same day for a separate defect, were republished 2026-09-27 under one burner-tip price rule (see get_gas_economics). Use get_gas_intelligence for pipeline, operator and parent-midstream data. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"state":{"description":"US state abbreviation, e.g. TX, VA, AZ. Returns the DCGI score and verdict, plus `gas_price_series` naming which EIA series priced the state.","type":"string"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"ef2a523d1e4546a16e25d8d054c6759332fc9c8f3ef56a95ad286eaa12aa9196","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_global_power","title":"Get Global Power","description":"Use this when the user asks about power plants worldwide or in a non-US country — operating AND the forward pipeline (announced / pre-construction / under-construction), across ALL fuels (coal, oil/gas, nuclear, solar, wind, hydro, bioenergy, geothermal). Global Energy Monitor Global Integrated Power Tracker: 182,000+ geolocated units across 170+ countries, each with fuel, capacity (MW), status, start year, operator/owner and lat/lng. Filter by country (e.g. Germany, India, Brazil, Japan), fuel (comma-union: coal, oil/gas, nuclear, solar, wind, hydro), status, pipeline=true (JUST the forward set: announced + pre-construction + construction), bbox (minLng,minLat,maxLng,maxLat), or min_mw. Returns a summary (total MW by fuel + count by status) plus the largest units. Answers \"what power is being built in India\", \"how much coal is still running in Vietnam\". Try: get_global_power country=India pipeline=true. Do NOT use for US grid telemetry/headroom (use get_grid_intelligence / get_grid_scoreboard) or the US planned-generator feed (use get_power_pipeline) — this is the GLOBAL asset inventory. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"country":{"description":"Country/area name to filter, e.g. Germany, India, Brazil, Japan","type":"string"},"fuel":{"description":"Fuel/type filter, comma-separated for a union: coal, oil/gas, nuclear, solar, wind, hydro, bioenergy, geothermal","type":"string"},"status":{"description":"Status substring filter, e.g. operating, construction, pre-construction, announced","type":"string"},"pipeline":{"description":"true = ONLY the forward pipeline (announced + pre-construction + under-construction)","type":"boolean"},"bbox":{"description":"Viewport filter as minLng,minLat,maxLng,maxLat","type":"string"},"min_mw":{"description":"Minimum unit capacity in MW","type":"number"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"97f6a7fa222aefa591064af8b4d241465faa0a0a049c08f302922e3853202f74","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_grid_data","title":"Live Grid Data","description":"Use this when the user asks for live electricity grid data (power demand, fuel mix) for one grid: the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), TVA, BPA, 40+ US utility balancing authorities (e.g. AZPS, SOCO, DUK, FPL, or a city: PHOENIX, ATLANTA), Canada (IESO, AESO, HYDROQUEBEC), Great Britain (NGESO), any ENTSO-E bidding zone (EU_DE_LU, EU_FR, EU_NL ...), Taiwan (TAIPOWER), Japan (OCCTO), South Korea (KEPCO-KR), Brazil (ONS), Australia (AEMO) or Singapore (EMA). US ISOs and EIA regions return EIA hourly fuel mix, demand and the 24h curve; other grids return each feed's newest reading per metric, each with its own timestamp. For PJM it also returns installed_capacity_mw: EIA-860M installed generating capacity (net summer MW of operating generators for the report month in installed_capacity_mw_period). That is not PJM committed capacity, which is listed in licence_withheld with no value. Raw telemetry for one grid; do NOT use for power-availability, time-to-power or interconnection-queue analysis (use get_grid_intelligence), nor for retail/gas pricing (use get_energy_prices). To rank many grids at once use get_grid_scoreboard. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"iso":{"description":"Grid code (required): a US ISO (ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE), TVA, BPA, a utility BA or city (AZPS, PHOENIX), or a non-US grid (IESO, AESO, HYDROQUEBEC, NGESO, EU_DE_LU, TAIPOWER, OCCTO, KEPCO-KR, ONS, AEMO, EMA)","type":"string"},"metric":{"description":"Optional metric focus, e.g. fuel_mix, demand, demand_curve","type":"string"},"period":{"description":"Optional time window for the metric, e.g. 24h","type":"string"},"mpp_pay":{"description":"Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.","type":"boolean"},"mpp_credential":{"description":"Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"70ce351e5a864946b30e70e1e040c8e9df0a1749f5cc9cc60757d1ce18a54b3d","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_grid_scoreboard","title":"Grid Scoreboard","description":"Use this when the user asks how power grids compare: demand, fuel mix or renewable share. GLOBAL grid scoreboard — 9 US grid operators (the 7 US ISOs PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, plus BPA and TVA) + Great Britain (NESO) + the European bidding zones (Germany, France, Netherlands, Italy/Milan, Spain, Poland, Switzerland, Portugal, the Nordics + Central/Eastern Europe — via ENTSO-E; the exact live-vs-configured count is in counts_basis.eu_zones_live / eu_zones_configured, measured per call rather than asserted here) + Taiwan (Taipower) + Japan (OCCTO areas) + South Korea (KPX) + Brazil SIN (ONS), ranked side-by-side on each feed's LATEST PUBLISHED reading: renewable share %, gas share %, full fuel mix (gas/nuclear/coal/wind/solar/hydro MW), and demand. ★FRESHNESS IS NOT UNIFORM and every row says so: each carries mix_period, mix_age_hours and freshness_basis. Answers \"which grid is cleanest right now\", \"how is ERCOT doing at this moment\". Try: get_grid_scoreboard. Full guide: read resource dchub://tool-guides/get_grid_scoreboard For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"460e3d83d15efaae432f23ab889bd8dcd102f95484964074ba208266ff6a8dd3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_hosting_capacity","title":"Feeder Hosting Capacity","description":"Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. Published records from many utilities (e.g. Con Edison, National Grid NY/MA, NYSEG/RG&E, Rhode Island Energy, Orange & Rockland, Central Hudson, Eversource CT, BGE, Pepco/Delmarva/ACE, Dominion VA, Ameren Illinois, AEP Ohio & I&M, Xcel MN/CO, DTE, Avista; the no-args call lists current coverage). This is filed distribution-level truth, not a proximity proxy. Three ways to call it: lat+lon (+radius_km, default 25) for a point; utility or market for a whole published territory; NO ARGS for the coverage list of every market that has data. Answers \"can this feeder actually take 20 MW\", \"where can I plug in without waiting on a substation upgrade\". Try: get_hosting_capacity utility=\"Ameren Illinois\" capacity_type=load min_mw=5. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"lat":{"description":"Latitude of the point to search around, decimal degrees. Must be paired with lon.","type":"number"},"lon":{"description":"Longitude of the point to search around, decimal degrees. Must be paired with lat.","type":"number"},"latitude":{"description":"Alias for lat — either name works","type":"number"},"lng":{"description":"Alias for lon — either name works","type":"number"},"longitude":{"description":"Alias for lon — either name works","type":"number"},"radius_km":{"description":"Search radius in km around lat/lon (default 25, max 150). Ignored when utility/market is passed — that mode covers the utility's entire published extent.","type":"number","minimum":1,"maximum":150},"utility":{"description":"Utility or market name, case-insensitive substring — e.g. \"Ameren Illinois\", \"Con Edison\", \"Providence\". Searches that utility's whole published territory instead of a point radius. Call with NO arguments to list every covered utility.","type":"string"},"market":{"description":"Alias for utility — either name works (e.g. \"Northern Virginia · Richmond\", \"New York City · Westchester\").","type":"string"},"capacity_type":{"description":"Restrict to one published type: \"load\" (what a new data-center load can DRAW — the type that answers siting), \"gen\" (DER/generation EXPORT headroom — NOT available load), or \"bus_headroom\" (transmission bus MW).","type":"string"},"min_mw":{"description":"Only return feeders whose published capacity is at or above this many MW.","type":"number"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e06faffd7a5c4865da5b771657206cc215094b71ea016c12133d238fe59cce4f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_infra_projects","title":"Get Infra Projects","description":"Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. \"which interstate gas pipelines are under construction into Louisiana?\", \"what 345 kV transmission projects are planned in PJM by 2030?\", \"what new projects appeared since last month?\". COVERS: (1) natural gas pipeline projects US-wide from the EIA natural gas pipeline projects list (public domain) — operator, status (Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed), states crossed, capacity in MMcf/d, miles, cost in $M, diameter, FERC/state docket, in-service year; (2) transmission projects from five ISOs' own project lists — ERCOT (TPIT), PJM (RTEP), MISO (MTEP Appendix A), SPP (STEP) and ISO-NE (RSP list); NOT CAISO or NYISO, and not utilities outside those ISOs. Each ISO publishes a different grain (an upgrade or facility, not a whole project), so a row count is a count of upgrades. Answers \"what gas pipelines are being built into Louisiana, how much capacity do they add, and when do they enter service\". Try: get_infra_projects type=gas_pipeline state=LA status=Construction. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"type":{"description":"Which project list: gas_pipeline (EIA, US-wide), transmission (ERCOT TPIT, Texas only) or all (default)","type":"string","enum":["gas_pipeline","transmission","all"]},"state":{"description":"US state abbreviation, e.g. TX or LA. Gas projects match any state they cross; transmission projects are all TX","type":"string"},"status":{"description":"Status, case-insensitive; comma list allowed. Gas: Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed. Transmission: Planned, Conceptual, Under Construction, Completed, Cancelled","type":"string"},"min_capacity":{"description":"Gas only: minimum pipeline capacity in million cubic feet per day (MMcf/d), e.g. 1000. With type=all it narrows to gas projects","type":"number"},"min_kv":{"description":"Transmission only: minimum voltage in kilovolts (kV), e.g. 345. With type=all it narrows to transmission projects","type":"number"},"in_service_after":{"description":"Only projects entering service on or after this date (YYYY-MM-DD or YYYY). Gas compares the in-service year; transmission the actual, else projected, in-service date","type":"string"},"in_service_before":{"description":"Only projects entering service on or before this date (YYYY-MM-DD or YYYY)","type":"string"},"new_since":{"description":"Only projects DC Hub first saw on or after this date (YYYY-MM-DD). The initial backfill is never counted as new","type":"string"},"include_delisted":{"description":"Also return projects the latest source release no longer lists (completed, withdrawn or dropped). Default false","type":"boolean"},"limit":{"description":"Max results to return (1-500; default varies by tool)","type":"integer","minimum":1,"maximum":500}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"5619e99d3285cdd0453b61d76adc286fc8088ecd76d6dec5a487188657ff439a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_intelligence_index","title":"Market Intelligence Index","description":"Use this when the user asks how healthy a data center market is: composite score (0-100) aggregating supply/demand balance, vacancy, absorption velocity, fiber depth, power availability, and pricing trend. Returns the index value, percentile rank across the 300+ market set, 7d/30d trend direction, and underlying component scores. Answers \"is this market healthy\", \"how does Northern Virginia look overall right now\". Try: get_intelligence_index market=northern-virginia. Returns ONE composite health number for a market; do NOT use for the full market metric set (use get_market_intel) or to rank multiple markets (use rank_markets). For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"f6f8037b35de0156497b74382d24bfab2c856999b658514be924f831025daec7","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_interconnection_queue","title":"Interconnection Queue","description":"Use this when the user asks about grid interconnection queues: how congested an ISO's queue is or how much data-center load is waiting. Returns queued generation GW per ISO. The projects field changes shape: with iso= it is an array of per-project rows; without iso it is an all-ISO summary object (total, by_iso_count, top). ERCOT also returns its large-load (data-center) queue; other ISOs don't publish one. Keyless: a trimmed preview; free with an email-bound key. Ex: \"How deep is ERCOT's queue?\" iso optional (US ISO code); free = preview. For demand and headroom on the same ISO also call get_grid_intelligence. For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"iso":{"description":"ISO/RTO grid region to drill into: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE; omit for the all-ISO snapshot","type":"string"},"mpp_pay":{"description":"Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.","type":"boolean"},"mpp_credential":{"description":"Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.","type":"string"}}},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"65a73cfceda9f61bb85d3cea0b9b9c4718e7c2baf6b705246a90a08c0226e4a0","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_iso_context","title":"Get Iso Context","description":"Use this when you need a whole power grid (ISO) briefing for your context window — one call returns a token-budgeted context pack for a US ISO/RTO: live grid snapshot (demand, fuel-mix shares), DCPI verdict mix & grid economics across the ISO's tracked markets (queue wait, power cost, reserve margin), interconnection-queue depth with the largest projects, real-time benchmark LMP, the tracked DCPI market list, deep-dive narrative excerpts, and recent news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_tokens budget. Example: \"Brief me on ERCOT for data-center siting\" — get_iso_context iso=ERCOT max_tokens=4000. Params: iso (required: ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE); max_tokens (optional, 200-8000, default 4000). Returns {sections:[{id,title,text,tokens,as_of,cite}], used_tokens, omitted}. Do NOT use for raw single-ISO telemetry (use get_grid_data), the per-ISO decision brief with headroom/TTP (use get_grid_intelligence), multi-ISO scalar comparison (use compare_isos), or non-US grids (use get_grid_scoreboard); this is the narrative briefing pack. Cite \"DC Hub (dchub.cloud)\". iso is required (US ISO code). For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"iso":{"type":"string","description":"ISO/RTO grid region (required): ERCOT, PJM, MISO, CAISO, SPP, NYISO, ISONE"},"max_tokens":{"description":"Token budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent","type":"number"}},"required":["iso"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"74763ed32173abde59d4c6aab772e2a039c6add652553573caf790a59b243ad6","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"},{"serverName":"cloud.dchub/mcp-server","endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","name":"get_market_context","title":"Get Market Context","description":"Use this when you need a whole data center market briefing for your context window — one call returns a token-budgeted context pack for a data-center market: DCPI verdict, power & grid facts, the Claude-written 12-month outlook, M&A deals, construction pipeline, operator footprint, transaction comps, risk factors, and top news — each section with its own token count, as_of timestamp, and citable URL, greedily filled in that priority order under your max_tokens budget. Example: \"Brief me on the Columbus data-center market\" — get_market_context market=columbus max_tokens=4000. Params: market (required, market slug e.g. northern-virginia — valid slugs come from rank_markets); max_tokens (optional, 200-8000, default 4000). Returns {sections:[{id,title,text,tokens,as_of,cite}], used_tokens, omitted}. Do NOT use for a single metric (use get_market_dcpi_rank), the raw structured metric set (use get_market_intel), or cross-market ranking (use rank_markets); this is the narrative briefing pack. Cite \"DC Hub (dchub.cloud)\". For multi-step data center or energy questions, start with execute_plan.","inputSchema":{"type":"object","properties":{"market":{"type":"string","description":"Market slug (required), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank"},"max_tokens":{"description":"Token budget for the pack, 200-8000 (default 4000); sections are filled in priority order until the budget is spent","type":"number"}},"required":["market"]},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"ff0edf8ef522bbfe7bc67b2290076797d3bd3f7888bab0e19ba3cbe4304858e4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-14T02:46:34.877Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"2f977c61340a9ef757e26ac64b3238c658c9a9c844bc4a9e085991023112a033","protocol":"streamable-http","status":"indexed","toolCount":50,"observedAt":"2026-11-14T02:46:34.877Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"cloud.dchub/mcp-server":{"url":"https://dchub.cloud/mcp"}}},"Cursor":{"mcpServers":{"cloud.dchub/mcp-server":{"url":"https://dchub.cloud/mcp"}}},"VS Code":{"servers":{"cloud.dchub/mcp-server":{"type":"http","url":"https://dchub.cloud/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://dchub.cloud/mcp"},{"protocol":"mcp","package":"dchub-mcp-server","registryType":"npm","version":"2.12.59"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:cloud.dchub%2Fmcp-server","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/cloud.dchub%2Fmcp-server","name":"cloud.dchub/mcp-server","description":"Orchestration layer for data center and energy intelligence. Start with execute_plan.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://dchub.cloud/mcp"},{"protocol":"mcp","package":"dchub-mcp-server","registryType":"npm","version":"2.12.59"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://dchub.cloud","repositoryUrl":"https://github.com/azmartone67/dchub-mcp-server","version":"2.12.59"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"cloud.dchub/mcp-server","status":"online","lastCheckedAt":"2026-11-20T05:18:13.064Z","lastSuccessfulCheck":"2026-11-20T05:18:13.064Z","latencyMs":181,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T05:18:13.064Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T05:18:13.064Z"},"security":null,"timestamps":{"createdAt":"2026-11-16T09:04:01.871Z","updatedAt":"2026-11-16T09:04:01.871Z","observedAt":"2026-11-20T05:18:13.064Z"},"compatibility":{"serverVersion":"2.12.59","protocolVersions":[{"protocol":"mcp","version":null}]}}}}