Austin Oaks Payload Rescue
REMOTE · AO-PAYLOAD-RESCUE-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 24
Repair malformed JSON that fails a schema. Deterministic only; refuses to guess; signed receipt.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · ao-payload-rescue-production.up.railway.app
claude mcp add --transport http com-freshypenguin-ao-payload-rescue 'https://ao-payload-rescue-production.up.railway.app/mcp'
{
"mcpServers": {
"com-freshypenguin-ao-payload-rescue": {
"url": "https://ao-payload-rescue-production.up.railway.app/mcp"
}
}
} {
"servers": {
"com-freshypenguin-ao-payload-rescue": {
"type": "http",
"url": "https://ao-payload-rescue-production.up.railway.app/mcp"
}
}
} [mcp_servers.com-freshypenguin-ao-payload-rescue] url = "https://ao-payload-rescue-production.up.railway.app/mcp"
{
"$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 mcp add com-freshypenguin-ao-payload-rescue --url 'https://ao-payload-rescue-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
com-freshypenguin-ao-payload-rescue:
url: "https://ao-payload-rescue-production.up.railway.app/mcp" {
"McpServers": {
"com-freshypenguin-ao-payload-rescue": {
"Transport": "http",
"Url": "https://ao-payload-rescue-production.up.railway.app/mcp"
}
}
} assistant mcp add com-freshypenguin-ao-payload-rescue -t streamable-http -u 'https://ao-payload-rescue-production.up.railway.app/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +1
- Server version: 0.3.2 → 0.4.6 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://ao-payload-rescue-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ao-payload-rescue-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ao-payload-rescue-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://ao-payload-rescue-production.up.railway.app/mcp | HTTPS enforced | 301 | https://ao-payload-rescue-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rescue_payload Rescue a JSON payload ~413
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mappings | object | – | Optional explicit key renames, e.g. {"custId": "customer_id"}. Field equivalence is NEVER inferred without a rule here. |
| payload | – | yes | The JSON document that failed downstream. Any JSON value. |
| schema | object | yes | The JSON Schema the payload must satisfy. A supported subset; unsupported keywords are rejected, never ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| status | string | yes | – |
No examples provided.
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.