Is the Scanbimlabs Scanbim MCP server down?

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "acc_create_issue",
  "description": "Create a real issue (punchlist/QC item) in ACC Build's Issues module via the APS Construction Issues v1 API. Returns the ACC-generated issue_id which can be linked back to a model URN or a detected clash.\nWhen to use: detect_clashes flagged a critical clash, or a field user reports a QC defect, and you want to track it in ACC for assignment and closeout.\nWhen NOT to use: you want to file a formal information request between trades — use acc_create_rfi instead. You want a note on a model element ",
  "inputSchema": {
    "type": "object",
    "required": [
      "project_id",
      "title",
      "description"
    ],
    "properties": {
      "title": {
        "type": "string",
        "examples": [
          "Duct/beam clash at Level 3 gridline C-4"
        ],
        "description": "Short human-readable issue title, 1-255 chars. Shows up as the headline in ACC Issues UI."
      },
      "due_date": {
        "type": "string",
        "examples": [
          "2026-05-15"
        ],
        "description": "ISO 8601 calendar date (YYYY-MM-DD). Time component is ignored by ACC."
      },
      "priority": {
        "enum": [
          "critical",
          "high",
          "medium",
          "low"
        ],
        "type": "string",
        "examples": [
          "high"
        ],
        "description": "ACC issue priority. Defaults to 'medium' if omitted."
      },
      "project_id": {
        "type": "string",
        "examples": [
          "b.a4be0c34a-4a01-4b0e-9f1a-123456789abc"
        ],
        "description": "ACC project ID in either 'b.<uuid>' or plain '<uuid>' form (the worker strips the 'b.' prefix before calling the Issues endpoint). Obtainable via acc_list_projects."
      },
      "assigned_to": {
        "type": "string",
        "examples": [
          "[email protected]"
        ],
        "description": "ACC user ID (UUID) or email of the assignee. Pass null or omit to leave unassigned."
      },
      "description": {
        "type": "string",
        "examples": [
          "16\" supply duct (Mech-L3-SD-42) conflicts with W18x35 beam at elev 10'-6\". Reroute duct above beam per SMACNA, maintain 18\" clearance."
        ],
        "description": "Long-form issue body. Plain text; supports newlines. Include clash coordinates, trade impact, and suggested fix."
      },
      "linked_model_id": {
        "type": "string",
        "examples": [
          "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
        ],
        "description": "Optional APS URN linking this issue back to the source model. Stored for ScanBIM cross-referencing; not forwarded to ACC's linkedDocuments field."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "acc_create_rfi",
  "description": "Create a Request For Information in ACC Build's RFIs module via the APS Construction RFIs v1 API, in 'draft' status. Returns the ACC rfi_id.\nWhen to use: a trade or subcontractor needs formal information from the design team (unclear detail, conflicting spec, missing dimension) and you want a tracked paper trail.\nWhen NOT to use: the item is just a punchlist fix — use acc_create_issue. The question is internal to one trade — handle inside that trade's toolchain.\nAPS scopes: data:read data:write ",
  "inputSchema": {
    "type": "object",
    "required": [
      "project_id",
      "subject",
      "question"
    ],
    "properties": {
      "subject": {
        "type": "string",
        "examples": [
          "Confirm fireproofing thickness on W18 beams at Level 3"
        ],
        "description": "Short RFI subject line, 1-255 chars. Appears as the RFI headline in ACC."
      },
      "priority": {
        "enum": [
          "critical",
          "high",
          "medium",
          "low"
        ],
        "type": "string",
        "examples": [
          "high"
        ],
        "description": "RFI priority. Defaults to 'medium'."
      },
      "question": {
        "type": "string",
        "examples": [
          "Drawing S2.03 shows 1-hour rating on W18x35 beams but spec 07 81 00 calls for 2-hour. Which governs at Level 3?"
        ],
        "description": "Full question body sent to the design team. Plain text with newlines allowed."
      },
      "project_id": {
        "type": "string",
        "examples": [
          "b.a4be0c34a-4a01-4b0e-9f1a-123456789abc"
        ],
        "description": "ACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically). Obtainable via acc_list_projects."
      },
      "assigned_to": {
        "type": "string",
        "examples": [
          "[email protected]"
        ],
        "description": "ACC user ID (UUID) or email of the responder. Pass null or omit to leave unassigned."
      },
      "linked_clash_id": {
        "type": "string",
        "examples": [
          "Ducts_001_Structural Framing_002"
        ],
        "description": "Optional clash ID from detect_clashes output used to link this RFI back to the triggering clash. Stored for ScanBIM cross-referencing; not forwarded to ACC."
      },
      "linked_model_id": {
        "type": "string",
        "examples": [
          "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1tb2RlbHMvMTcwMDAwMDAwMDAwMF9idWlsZGluZy5ydnQ"
        ],
        "description": "Optional APS URN of the model the RFI references. Stored for ScanBIM cross-referencing; not forwarded to ACC."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "acc_list_issues",
  "description": "List up to 50 issues from an ACC project, optionally filtered by status and priority. Returns a normalized array of {id, title, status, priority, due_date}.\nWhen to use: you need a dashboard view of open issues, to find a specific issue by metadata, or to check the status of previously created issues.\nWhen NOT to use: you want the full audit trail of a single issue — the ACC Issues UI or the per-issue endpoint is better. This tool caps at 50 results and does no pagination.\nAPS scopes: data:read ",
  "inputSchema": {
    "type": "object",
    "required": [
      "project_id"
    ],
    "properties": {
      "status": {
        "type": "string",
        "examples": [
          "open"
        ],
        "description": "Filter by ACC issue status. Accepted values: 'open', 'closed', 'in_review', 'draft'. Omit for all statuses."
      },
      "priority": {
        "type": "string",
        "examples": [
          "high"
        ],
        "description": "Filter by priority: 'critical' | 'high' | 'medium' | 'low'. Omit for all priorities."
      },
      "project_id": {
        "type": "string",
        "examples": [
          "b.a4be0c34a-4a01-4b0e-9f1a-123456789abc"
        ],
        "description": "ACC project ID in 'b.<uuid>' or '<uuid>' form (the 'b.' prefix is stripped automatically). Obtainable via acc_list_projects."
      },
      "assigned_to": {
        "type": "string",
        "examples": [
          "[email protected]"
        ],
        "description": "Reserved for future filtering by assignee user ID or email. Currently not forwarded to the ACC API."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}