Remote MCP · Endpoint
AgentWork Outcome Router MCP server
No. AgentWork Outcome Router answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://agent-work-api.agentwork-market.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.mitchellOpZero/agentwork
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 275 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- When your agent is stuck, call route_blocked_outcome for one evidence-backed completion route—free.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 275 ms |
| 2 days ago | Handshake completed | 291 ms |
| 4 days ago | Handshake completed | 267 ms |
| 5 days ago | Handshake completed | 232 ms |
| 7 days ago | Handshake completed | 303 ms |
| 8 days ago | Handshake completed | 234 ms |
| 9 days ago | Handshake completed | 262 ms |
| 12 days ago | Handshake completed | 386 ms |
| 13 days ago | Handshake completed | 284 ms |
| 15 days ago | Handshake completed | 235 ms |
| 17 days ago | Handshake completed | 227 ms |
| 18 days ago | Handshake completed | 255 ms |
| 19 days ago | Handshake completed | 246 ms |
| 20 days ago | Handshake completed | 522 ms |
| 20 days ago | Handshake completed | 329 ms |
| 21 days ago | Handshake completed | 203 ms |
| 23 days ago | Handshake completed | 52 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.
Listing data comes from the official MCP registry. Glide is not affiliated with AgentWork Outcome Router and makes no claim about it beyond what these checks measured.