Remote MCP · Endpoint

Youth4work (public, no sign-in) MCP server

No. Youth4work (public, no sign-in) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.youth4work.com/public/mcp

The last check completed an MCP handshake.

Registry name
com.youth4work/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
328 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only search of Youth4work public jobs, assessed talent, exam mock tests and Indian colleges.
Listing
From the official MCP registry (active).
Recent checks of Youth4work (public, no sign-in)
CheckedResultHandshake
1 hour agoHandshake completed328 ms
2 days agoHandshake completed176 ms
5 days agoHandshake completed152 ms
7 days agoHandshake completed180 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed232 ms
13 days agoHandshake completed214 ms
15 days agoHandshake completed173 ms
17 days agoHandshake completed208 ms
19 days agoHandshake completed137 ms
20 days agoHandshake completed226 ms
21 days agoHandshake completed334 ms
23 days agoHandshake completed205 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 Youth4work (public, no sign-in) and makes no claim about it beyond what these checks measured.