Remote MCP · Endpoint
Retry-outcome resolution dedup proxy MCP server
No. Retry-outcome resolution dedup proxy answered an MCP handshake 27 minutes ago.
UpLast checked 27 minutes ago
Server URL
https://textforagents.com/products/retry-outcome-resolution-dedup-proxy/mcp
The last check completed an MCP handshake.
- Registry name
- com.textforagents/retry-outcome-resolution-dedup-proxy
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 43 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Dedup proxy: claim-before-execute, UNKNOWN resolution, CONFLICT and ESCALATED refusal.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 27 minutes ago | Handshake completed | 43 ms |
| 10 days ago | Handshake completed | 42 ms |
| 11 days ago | Handshake completed | 44 ms |
| 12 days ago | Handshake completed | 86 ms |
| 13 days ago | Handshake completed | 48 ms |
| 14 days ago | Handshake completed | 48 ms |
| 15 days ago | Handshake completed | 46 ms |
| 16 days ago | Handshake completed | 44 ms |
| 17 days ago | Handshake completed | 58 ms |
| 19 days ago | Handshake completed | 45 ms |
| 22 days ago | Handshake completed | 45 ms |
| 24 days ago | Handshake completed | 43 ms |
| 27 days ago | Handshake completed | 23 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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.
Listing data comes from the official MCP registry. Glide is not affiliated with Retry-outcome resolution dedup proxy and makes no claim about it beyond what these checks measured.