Remote MCP · Endpoint

Jobs Base MCP server

No. Jobs Base answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://jobsbase.io/mcp

The last check completed an MCP handshake.

Registry name
io.jobsbase/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
454 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search builder roles - jobs where one person owns engineering, product, and QA end-to-end.
Listing
From the official MCP registry (active).
Recent checks of Jobs Base
CheckedResultHandshake
9 hours agoHandshake completed454 ms
2 days agoHandshake completed642 ms
4 days agoHandshake completed488 ms
5 days agoHandshake completed76 ms
7 days agoHandshake completed488 ms
8 days agoHandshake completed293 ms
9 days agoHandshake completed338 ms
12 days agoHandshake completed301 ms
13 days agoHandshake completed242 ms
15 days agoHandshake completed486 ms
16 days agoHandshake completed263 ms
17 days agoHandshake completed37 ms
19 days agoHandshake completed519 ms
19 days agoHandshake completed67 ms
20 days agoHandshake completed353 ms
21 days agoHandshake completed430 ms
23 days agoHandshake completed45 ms

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

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