Remote MCP · Endpoint

JobCrawls MCP server

No. JobCrawls answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.jobcrawls.com/api/connector

The last check completed an MCP handshake.

Registry name
com.jobcrawls/connector
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search jobs in Finland and calculate net salary. Read-only, no login. English, Finnish, Swedish.
Listing
From the official MCP registry (active).
Recent checks of JobCrawls
CheckedResultHandshake
2 hours agoHandshake completed152 ms
2 days agoHandshake completed137 ms
5 days agoHandshake completed150 ms
7 days agoHandshake completed206 ms
9 days agoHandshake completed143 ms
11 days agoHandshake completed178 ms
13 days agoHandshake completed209 ms
15 days agoHandshake completed150 ms
17 days agoHandshake completed155 ms
19 days agoHandshake completed194 ms
20 days agoHandshake completed197 ms
21 days agoHandshake completed207 ms
22 days agoHandshake completed140 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 JobCrawls and makes no claim about it beyond what these checks measured.