Remote MCP · Endpoint

Austin Oaks Payload Rescue MCP server

Yes, as of 9 hours ago: the server returned an HTTP error.

DownLast checked 9 hours ago

Server URL

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

The last check failed: the server returned an HTTP error.

Registry name
com.freshypenguin/ao-payload-rescue
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
64.7% from 17 checks
Described by its publisher as
Repair malformed JSON that fails a schema. Deterministic only; refuses to guess; signed receipt.
Website
https://ao-payload-rescue-production.up.railway.app/mcp/info
Listing
From the official MCP registry (active).
Recent checks of Austin Oaks Payload Rescue
CheckedResultHandshake
9 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed26 ms
12 days agoHandshake completed23 ms
13 days agoHandshake completed22 ms
15 days agoHandshake completed29 ms
16 days agoHandshake completed29 ms
17 days agoHandshake completed30 ms
19 days agoHandshake completed21 ms
19 days agoHandshake completed23 ms
20 days agoHandshake completed23 ms
21 days agoHandshake completed41 ms
22 days agoHandshake completed26 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Austin Oaks Payload Rescue and makes no claim about it beyond what these checks measured.