# Austin Oaks Payload Rescue

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

- name: com.freshypenguin/ao-payload-rescue
- version: 0.3.2
- connection class: unknown (unknown)
- trust: 50/100 flags: no-repository, unreachable
- quality: 88/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.freshypenguin%2Fao-payload-rescue
- tools: https://api.protogrid.dev/v1/servers/com.freshypenguin%2Fao-payload-rescue/tools

**Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "ao-payload-rescue": {
      "type": "http",
      "url": "https://ao-payload-rescue-production.up.railway.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 0
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website -unreachable(7 failures) ~updated-43d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 88/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 1 of 1 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 558 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 1, about 558 tokens to load them all
- tool set hash: 26086e0110924085e942b396e97bea45
- badge: [![protogrid quality](https://protogrid.dev/badge/com.freshypenguin/ao-payload-rescue.svg)](https://protogrid.dev/servers/com.freshypenguin/ao-payload-rescue)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://ao-payload-rescue-production.up.railway.app/mcp (streamable-http, auth none, reachable false, uptime30d 0.9027778)

## Packages

_none_

## Tools (1)

- `rescue_payload`: 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.