Remote MCP · Endpoint

jopp MCP server

No. jopp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jopp.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.jopp/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Search open jobs in Switzerland and Liechtenstein and read jopp job briefs.
Listing
From the official MCP registry (active).
Recent checks of jopp
CheckedResultHandshake
1 hour agoHandshake completed160 ms
11 hours agoHandshake completed222 ms
1 day agoHandshake completed193 ms
2 days agoHandshake completed181 ms
4 days agoHandshake completed154 ms
4 days agoHandshake completed164 ms
5 days agoHandshake completed244 ms
6 days agoHandshake completed398 ms
8 days agoHandshake completed590 ms
11 days agoHandshake completed159 ms
13 days agoHandshake completed149 ms
16 days agoHandshake completed166 ms
18 days agoHandshake completed175 ms
20 days agoHandshake completed303 ms
22 days agoHandshake completed372 ms
24 days agoHandshake completed961 ms

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

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