# Austin Oaks Payload Rescue (remote · ao-payload-rescue-production.up.railway.app)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `ao-payload-rescue-production.up.railway.app`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production.md), [page](https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production)

## Channel facts

- Endpoint: `https://ao-payload-rescue-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 458 tokens (~458/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Austin Oaks Payload Rescue MCP server?

Austin Oaks Payload Rescue is a hosted endpoint at https://ao-payload-rescue-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-freshypenguin-ao-payload-rescue 'https://ao-payload-rescue-production.up.railway.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-freshypenguin-ao-payload-rescue]
url = "https://ao-payload-rescue-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-freshypenguin-ao-payload-rescue": {
      "type": "remote",
      "url": "https://ao-payload-rescue-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-freshypenguin-ao-payload-rescue --url 'https://ao-payload-rescue-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-freshypenguin-ao-payload-rescue:
    url: "https://ao-payload-rescue-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-freshypenguin-ao-payload-rescue": {
      "Transport": "http",
      "Url": "https://ao-payload-rescue-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-freshypenguin-ao-payload-rescue -t streamable-http -u 'https://ao-payload-rescue-production.up.railway.app/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 72, +1)

- [functional] Server version: 0.3.2 → 0.4.6

## MCP tools (1)

### `rescue_payload` (~413 tokens)

Rescue a JSON 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.

Input parameters:

- `mappings` (object): Optional explicit key renames, e.g. {"custId": "customer_id"}. Field equivalence is NEVER inferred without a rule here.
- `payload` (required): The JSON document that failed downstream. Any JSON value.
- `schema` (object, required): The JSON Schema the payload must satisfy. A supported subset; unsupported keywords are rejected, never ignored.

Output parameters:

- `changes` (array): Every repair applied, with a JSON path.
- `original_hash` (string)
- `path` (string|null)
- `problems` (array): Every blocking issue, with a stable reason code.
- `reason_code` (string|null)
- `receipt` (object): Hashes and a signature. No payload content.
- `receipt_id` (string)
- `repaired_hash` (string|null)
- `repaired_payload`: Null when status is CANNOT_REPAIR.
- `schema_valid` (boolean)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 78
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71

## Common questions

### What is the Austin Oaks Payload Rescue MCP server?

Austin Oaks Payload Rescue is an MCP server listed in the public MCP registry as com.freshypenguin/ao-payload-rescue. Repair malformed JSON that fails a schema. Deterministic only; refuses to guess; signed receipt. This page covers its hosted endpoint (https://ao-payload-rescue-production.up.railway.app/mcp).

### Is the Austin Oaks Payload Rescue MCP server safe to use?

Austin Oaks Payload Rescue scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Austin Oaks Payload Rescue MCP server expose?

Austin Oaks Payload Rescue exposes 1 tool: rescue_payload. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.

### Does the Austin Oaks Payload Rescue MCP server require authentication?

No. We connected to Austin Oaks Payload Rescue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Austin Oaks Payload Rescue MCP server still maintained?

Austin Oaks Payload Rescue is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ao-payload-rescue-production.up.railway.app/mcp
- Website: https://ao-payload-rescue-production.up.railway.app/mcp/info
- Changelog RSS feed: https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production.json
- HTML version of this page: https://verifymcp.io/servers/com-freshypenguin-ao-payload-rescue/ao-payload-rescue-production