Remote MCP · Endpoint

Jobpost MCP server

No. Jobpost answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://jobpost.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/jobpost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
419 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Read the job posting from any career page: title, employer, dates, salary. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Jobpost
CheckedResultHandshake
53 minutes agoHandshake completed419 ms
2 days agoHandshake completed416 ms
4 days agoHandshake completed509 ms
5 days agoHandshake completed417 ms
7 days agoHandshake completed473 ms
8 days agoHandshake completed418 ms
9 days agoHandshake completed2.59 s
12 days agoHandshake completed404 ms
13 days agoHandshake completed409 ms
15 days agoHandshake completed409 ms
17 days agoHandshake completed398 ms
18 days agoHandshake completed402 ms
19 days agoHandshake completed398 ms
20 days agoHandshake completed403 ms
21 days agoHandshake completed414 ms
21 days agoHandshake completed599 ms

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

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