Remote MCP · Endpoint

Swissmote public jobs MCP server

No. Swissmote public jobs answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://api.swissmote.com/v2/api/public/mcp

The last check completed an MCP handshake.

Registry name
io.github.theguysaccount/swissmote
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
26 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 9 checks
Described by its publisher as
Search published Swissmote openings with public apply links and confidentiality controls.
Listing
From the official MCP registry (active).
Recent checks of Swissmote public jobs
CheckedResultHandshake
4 days agoHandshake completed26 ms
7 days agoHandshake completed24 ms
16 days agoHandshake completed33 ms
17 days agoHandshake completed28 ms
18 days agoHandshake completed27 ms
19 days agoHandshake completed26 ms
21 days agoHandshake completed27 ms
22 days agoHandshake completed26 ms
22 days agoHandshake completed33 ms

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

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