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).
Recent checks of AgentWork Outcome Router
CheckedResultHandshake
2 hours agoHandshake completed275 ms
2 days agoHandshake completed291 ms
4 days agoHandshake completed267 ms
5 days agoHandshake completed232 ms
7 days agoHandshake completed303 ms
8 days agoHandshake completed234 ms
9 days agoHandshake completed262 ms
12 days agoHandshake completed386 ms
13 days agoHandshake completed284 ms
15 days agoHandshake completed235 ms
17 days agoHandshake completed227 ms
18 days agoHandshake completed255 ms
19 days agoHandshake completed246 ms
20 days agoHandshake completed522 ms
20 days agoHandshake completed329 ms
21 days agoHandshake completed203 ms
23 days agoHandshake completed52 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.