Remote MCP · Endpoint

Jobven MCP server

No. Jobven answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://api.jobven.com/mcp

The last check completed an MCP handshake.

Registry name
com.jobven/jobven
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search job postings and employers from company career sites; each result returns its REST call.
Website
https://jobven.com/docs/mcp
Listing
From the official MCP registry (active).
Recent checks of Jobven
CheckedResultHandshake
35 minutes agoHandshake completed360 ms
8 days agoHandshake completed76 ms
9 days agoHandshake completed64 ms
11 days agoHandshake completed211 ms
12 days agoHandshake completed232 ms
12 days agoHandshake completed87 ms
14 days agoHandshake completed58 ms
14 days agoHandshake completed72 ms
16 days agoHandshake completed122 ms
19 days agoHandshake completed124 ms
21 days agoHandshake completed205 ms
24 days agoHandshake completed155 ms
26 days agoHandshake completed70 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Jobven and makes no claim about it beyond what these checks measured.