Remote MCP · Endpoint

JOA — Job Opportunities API MCP server

No. JOA — Job Opportunities API answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.jobopportunitiesapi.org/mcp

The last check completed an MCP handshake.

Registry name
org.jobopportunitiesapi/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
558 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search live employer-direct job postings, company hiring signal, market stats and the change feed.
Listing
From the official MCP registry (active).
Recent checks of JOA — Job Opportunities API
CheckedResultHandshake
7 hours agoHandshake completed558 ms
3 days agoHandshake completed426 ms
12 days agoHandshake completed429 ms
12 days agoHandshake completed423 ms
14 days agoHandshake completed403 ms
15 days agoHandshake completed404 ms
16 days agoHandshake completed413 ms
17 days agoHandshake completed400 ms
18 days agoHandshake completed406 ms
20 days agoHandshake completed602 ms
22 days agoHandshake completed416 ms
25 days agoHandshake completed1.25 s
27 days agoHandshake completed401 ms
29 days agoHandshake completed448 ms

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

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 JOA — Job Opportunities API and makes no claim about it beyond what these checks measured.