Remote MCP · Endpoint

io.github.work0r-ai/workorai MCP server

No. io.github.work0r-ai/workorai answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://workorai.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.work0r-ai/workorai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
308 ms
Tools exposed
29 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
WorkorAI talent marketplace MCP: candidate job search and employer hiring with explainable matching
Listing
From the official MCP registry (active).
Recent checks of io.github.work0r-ai/workorai
CheckedResultHandshake
3 hours agoHandshake completed308 ms
9 days agoHandshake completed362 ms
10 days agoHandshake completed337 ms
11 days agoHandshake completed1.52 s
12 days agoHandshake completed288 ms
14 days agoHandshake completed300 ms
14 days agoHandshake completed304 ms
15 days agoHandshake completed303 ms
17 days agoHandshake completed312 ms
19 days agoHandshake completed313 ms
21 days agoHandshake completed303 ms
24 days agoHandshake completed320 ms
26 days agoHandshake completed299 ms
28 days agoHandshake completed294 ms

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

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 io.github.work0r-ai/workorai and makes no claim about it beyond what these checks measured.