Is the Dchub Datacenter Power Grid Fiber MCP server down?

• Added "type":"string" to untyped parameters: geometry. Change to number/boolean/array where that's what you accept. (verify)

{
  "name": "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, rolling out by data-center market — Loudoun County VA first; 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 pe",
  "inputSchema": {
    "type": "object",
    "properties": {
      "lat": {
        "type": "number",
        "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"
      },
      "lng": {
        "type": "number",
        "description": "Alias for lon — either name works"
      },
      "lon": {
        "type": "number",
        "description": "Longitude of a point ON the parcel (used with lat when geometry is omitted)"
      },
      "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",
        "type": "string"
      },
      "latitude": {
        "type": "number",
        "description": "Alias for lat — either name works"
      },
      "longitude": {
        "type": "number",
        "description": "Alias for lon — either name works"
      },
      "capacity_mw": {
        "type": "number",
        "description": "Optional target load in MW to pass through into the site_evaluation_handoff"
      }
    }
  },
  "annotations": {
    "access": "free_preview",
    "maturity": "unknown",
    "connect_url": "https://dchub.cloud/connect?ref=mcp-tools-list&tool=analyze_parcel",
    "readOnlyHint": true,
    "openWorldHint": false,
    "tier_required": "anonymous",
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Analyze Parcel"
}

• Added "type":"string" to untyped parameters: candidate_ids. Change to number/boolean/array where that's what you accept. (verify)

{
  "name": "cluster_sites_by_latency",
  "description": "Use this when the user asks which data center sites can form a low-latency cluster (2-8 sites) — returns viable low-latency clusters and pairwise RTT floors before any routing work. Use when your human wants to know which of N candidate sites can form a synchronous / low-latency cluster (sync replication, active-active pairs, HPC pods): deterministic pruning BEFORE detailed routing. Per site pair: haversine distance, round-trip physics floor (km × 4.9 µs/km — light in SMF-28 fiber, n≈1.468 — the",
  "inputSchema": {
    "type": "object",
    "properties": {
      "sites": {
        "type": "string",
        "description": "Semicolon-separated \"lat,lon\" pairs, 2-8 sites (same format as compare_sites locations); optional per-site labels via \"lat,lon:label\", e.g. \"39.04,-77.48:ashburn;39.29,-76.61:baltimore\"."
      },
      "candidate_ids": {
        "description": "Array (or comma-separated string) of candidate_id values from get_refined_queue — each resolves to its FROZEN mint coordinates (zero transcription drift); expired/unknown are dropped and declared in candidate_contract.",
        "type": "string"
      },
      "max_latency_us": {
        "type": "number",
        "maximum": 10000000,
        "minimum": 1,
        "description": "Round-trip latency budget in microseconds (default 1000 µs = 1 ms; sync replication is typically 1000-2000 µs)"
      },
      "min_confidence": {
        "type": "string",
        "description": "Minimum evidence tier a pair must meet to count as viable: \"published\" | \"tracked\" | \"inferred\" (default inferred = include all)"
      }
    }
  },
  "annotations": {
    "access": "free",
    "problem": "fiber routes, diversity and latency",
    "maturity": "mature",
    "front_door": "get_fiber_intel",
    "connect_url": "https://dchub.cloud/connect?ref=mcp-tools-list&tool=cluster_sites_by_latency",
    "readOnlyHint": true,
    "openWorldHint": false,
    "tier_required": "anonymous",
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Cluster Sites By Latency"
}

• Added "type":"string" to untyped parameters: sites. Change to number/boolean/array where that's what you accept. (verify)

{
  "name": "compare_sites",
  "description": "Use this when the user has 2-4 candidate data center sites and asks which is best. Pass locations as \"lat,lon;lat,lon\" and optional capacity_mw. Returns each site's analyze_site scores side by side plus a recommended winner and why. Keyless returns each site's verdict band and power band, with the other factors named; a free key adds names and counts without figures; scores and figures need a paid DC Hub plan, as does the pick. Ex: \"Phoenix vs Ashburn for 50 MW?\"",
  "inputSchema": {
    "type": "object",
    "properties": {
      "sites": {
        "description": "Alternative to locations: an array of {lat, lon} (or {lat, lng}) objects, 2-4 sites",
        "type": "string"
      },
      "mpp_pay": {
        "type": "boolean",
        "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."
      },
      "locations": {
        "type": "string",
        "description": "Semicolon-separated list of 2-4 \"lat,lon\" pairs to compare, e.g. \"33.45,-112.07;39.04,-77.48\""
      },
      "capacity_mw": {
        "type": "number",
        "description": "Target power load for the build in megawatts (MW), e.g. 50 (typical 50-500)"
      },
      "mpp_credential": {
        "type": "string",
        "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."
      }
    }
  },
  "annotations": {
    "access": "paid",
    "maturity": "unknown",
    "pricing_url": "https://dchub.cloud/pricing/upgrade?tool=compare_sites&ref=mcp-tools-list",
    "readOnlyHint": true,
    "openWorldHint": false,
    "tier_required": "pro",
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Compare Sites"
}