Remote MCP · Endpoint

JobSlop MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://jobslop.io/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
io.jobslop/jobslop
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Check US job listings for ghost-job warning signs: look up a job link, search jobs, company reports.
Listing
From the official MCP registry (active).
Recent checks of JobSlop
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
19 hours agoFailed - the check failed for an unclassified reason—
2 days agoHandshake completed71 ms
3 days agoHandshake completed1.51 s
4 days agoHandshake completed64 ms
5 days agoHandshake completed115 ms
6 days agoHandshake completed83 ms
8 days agoHandshake completed76 ms
10 days agoHandshake completed48 ms
13 days agoHandshake completed75 ms
15 days agoHandshake completed283 ms
17 days agoHandshake completed53 ms
19 days agoHandshake completed50 ms
21 days agoHandshake completed47 ms

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

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