Is the Ojaskord Data Compliance MCP server down?

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

{
  "name": "get_safety_report",
  "description": "Retrieves a detailed compliance report and remediation strategy for a flagged payload. Call this BEFORE your agent decides whether to proceed, redact, or halt -- immediately after validate_data_safety returns REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE. Use this when validate_data_safety has returned a non-SAFE verdict and your agent needs the specific regulation triggered, the problematic fields, and a compliant reformulation before acting. Returns the specific regulation triggered, exact ",
  "inputSchema": {
    "type": "object",
    "required": [
      "mode"
    ],
    "properties": {
      "mode": {
        "enum": [
          "REPORT",
          "BATCH",
          "AUDIT"
        ],
        "type": "string",
        "description": "REPORT: get redaction strategy and compliant reformulation for a flagged payload. BATCH: classify up to 50 payloads. AUDIT: generate compliance summary report."
      },
      "context": {
        "type": "string",
        "description": "What will be done with this data. Used to improve verdict accuracy."
      },
      "payload": {
        "type": "string",
        "description": "The flagged payload to analyse. Required for REPORT mode."
      },
      "payloads": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Array of data payloads to classify. Required for BATCH mode. Maximum 50."
      },
      "jurisdiction": {
        "type": "string",
        "description": "Jurisdiction override for REPORT mode (e.g. \"EU\", \"US\", \"UK\"). Optional."
      },
      "dataset_description": {
        "type": "string",
        "description": "Description of the dataset for AUDIT mode (e.g. \"customer CRM records including name, email, purchase history, and UK addresses\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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

{
  "name": "validate_data_safety",
  "description": "Validates a data payload against GDPR, HIPAA, PCI-DSS, and other frameworks. Call this BEFORE your agent passes any assembled payload to an external API, writes it to a database, or transmits it via any third-party service -- at the moment the payload is assembled and no external call has been made, including any Stripe MPP, Alipay AI Pay, Shopify UCP, or third-party API call. Use this when your agent has assembled user-sourced or API-response data and is about to write it to storage or transmit",
  "inputSchema": {
    "type": "object",
    "required": [
      "payload"
    ],
    "properties": {
      "context": {
        "type": "string",
        "description": "What your agent is about to do with this data (e.g. \"write to database\", \"send to third-party API\", \"log to file\", \"pass to email tool\"). Improves verdict accuracy."
      },
      "payload": {
        "type": "string",
        "description": "The data payload to classify. Can be any string, JSON object as string, form data, API response, or text content. The payload is analysed in memory and immediately discarded — never stored or logged."
      },
      "jurisdiction": {
        "type": "string",
        "description": "Override jurisdiction if known (e.g. \"EU\", \"US\", \"UK\", \"CA\", \"AU\"). Use if data_origin_ip is unavailable but jurisdiction is known."
      },
      "data_origin_ip": {
        "type": "string",
        "description": "IP address of the data subject or data source. Used to detect applicable jurisdiction and regulations (GDPR if EU, CCPA if US, etc). Optional but improves regulatory accuracy."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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

{
  "name": "validate_data_safety_lite",
  "description": "Validates a payload for sensitive patterns without AI classification. Call this BEFORE pre-screening high-volume payloads when pattern detection is sufficient and AI classification is not required. Use this when your agent is processing a large volume of payloads in batch and needs a fast pattern-only filter before selectively invoking full AI classification on flagged items. Returns SAFE_TO_PROCESS / REVIEW_REQUIRED in under 100ms -- no AI, no IP check, no jurisdiction lookup. Treating a SAFE_T",
  "inputSchema": {
    "type": "object",
    "required": [
      "payload"
    ],
    "properties": {
      "context": {
        "type": "string",
        "description": "Optional: what your agent plans to do with this data."
      },
      "payload": {
        "type": "string",
        "description": "The data payload to screen for sensitive patterns."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}