Remote MCP · Endpoint

ApplyAll MCP server

No. ApplyAll answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://applyall.com/mcp

The last check completed an MCP handshake.

Registry name
com.applyall/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
127 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search for jobs and apply to jobs.
Listing
From the official MCP registry (active).
Recent checks of ApplyAll
CheckedResultHandshake
1 hour agoHandshake completed127 ms
1 day agoHandshake completed148 ms
3 days agoHandshake completed140 ms
3 days agoHandshake completed138 ms
4 days agoHandshake completed120 ms
5 days agoHandshake completed220 ms
7 days agoHandshake completed118 ms
10 days agoHandshake completed245 ms
12 days agoHandshake completed111 ms
14 days agoHandshake completed143 ms
17 days agoHandshake completed107 ms
19 days agoHandshake completed144 ms
21 days agoHandshake completed132 ms
23 days agoHandshake completed121 ms
25 days agoHandshake completed121 ms
26 days agoHandshake completed100 ms
28 days agoHandshake completed137 ms
29 days agoHandshake completed180 ms

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

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 ApplyAll and makes no claim about it beyond what these checks measured.