Austin Oaks Payload Rescue

Repair malformed JSON that fails a schema. Deterministic only; refuses to guess; signed receipt.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
93%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~675Tokens (definiciones de herramientas)
~3.8 KBTamaño de respuesta típico
Impacto moderado en la atención (0.53% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "ao-payload-rescue": {
      "url": "https://ao-payload-rescue-production.up.railway.app/mcp"
    }
  }
}

Puntos de conexión remotos

https://ao-payload-rescue-production.up.railway.app/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (1)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢rescue_payload(payload, schema, mappings)

Repair a malformed JSON or API payload so it matches a required schema. Use when a request, webhook, or tool output was rejected for schema validation errors: wrong types, a null where an array or object belongs, a forbidden extra property, or mismatched keys between two APIs. Deterministic repairs only. No semantic guessing. Refuses instead of inventing a value, and returns an exact change manifest plus a signed receipt so a silent 'fix' can never pass downstream unrecorded. Give it the payload that was rejected and the JSON Schema it failed. It returns one of: VALID the payload already conformed; nothing changed REPAIRED safely repaired; the returned payload satisfies the schema CANNOT_REPAIR no safe repair exists; repaired_payload is null on purpose INVALID_SCHEMA the schema is malformed or uses an unsupported keyword ERROR bad request, or a size/depth limit was exceeded It repairs structure only: unambiguous type coercion, null to empty array or object, removing a property the contract forbids, renaming a key when an explicit mapping rule is supplied, and trimming whitespace that is blocking validation. It will NOT invent a value. A missing required field, an ambiguous number like "1,234.00", an identifier like "007" that would lose its leading zeros, or a date like "09/06/2026" whose day/month order is unknown all return CANNOT_REPAIR with a stable reason code rather than a guess. No language model is involved. The same input always produces the same output and the same receipt id.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "payload": {
      "description": "The JSON document that failed downstream. Any JSON value."
    },
    "schema": {
      "type": "object",
      "description": "The JSON Schema the payload must satisfy. A supported subset; unsupported keywords are rejected, never ignored."
    },
    "mappings": {
      "type": "object",
      "additionalProperties": {
        "type": "string"
      },
      "description": "Optional explicit key renames, e.g. {\"custId\": \"customer_id\"}. Field equivalence is NEVER inferred without a rule here."
    }
  },
  "required": [
    "payload",
    "schema"
  ],
  "additionalProperties": false
}

Esquema de salida

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "VALID",
        "REPAIRED",
        "CANNOT_REPAIR",
        "INVALID_SCHEMA",
        "ERROR"
      ]
    },
    "schema_valid": {
      "type": "boolean"
    },
    "repaired_payload": {
      "description": "Null when status is CANNOT_REPAIR."
    },
    "changes": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Every repair applied, with a JSON path."
    },
    "problems": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Every blocking issue, with a stable reason code."
    },
    "reason_code": {
      "type": [
        "string",
        "null"
      ]
    },
    "path": {
      "type": [
        "string",
        "null"
      ]
    },
    "receipt": {
      "type": "object",
      "description": "Hashes and a signature. No payload content."
    },
    "receipt_id": {
      "type": "string"
    },
    "original_hash": {
      "type": "string"
    },
    "repaired_hash": {
      "type": [
        "string",
        "null"
      ]
    }
  },
  "required": [
    "status",
    "schema_valid"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada1 herramientas
verificadoversión no registrada1 herramientas
verificadoversión no registrada1 herramientas