Remote MCP · Endpoint
Liepin Jobs MCP server
No. Liepin Jobs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://open-agent.liepin.com/mcp/user
The last check completed an MCP handshake.
- Registry name
- io.github.xllinbupt/liepin-jobs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 702 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 57.9% from 19 checks
- Described by its publisher as
- Liepin job search and resume workflows backed by the official Liepin MCP server.
- Repository
- https://github.com/xllinbupt/MCP2skill
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 702 ms |
| 1 day ago | Handshake completed | 689 ms |
| 2 days ago | Failed - the connection was refused or dropped | — |
| 3 days ago | Failed - the connection was refused or dropped | — |
| 4 days ago | Handshake completed | 681 ms |
| 5 days ago | Failed - the connection was refused or dropped | — |
| 6 days ago | Handshake completed | 725 ms |
| 8 days ago | Failed - the connection was refused or dropped | — |
| 11 days ago | Failed - the connection was refused or dropped | — |
| 13 days ago | Failed - the connection was refused or dropped | — |
| 15 days ago | Handshake completed | 684 ms |
| 18 days ago | Handshake completed | 796 ms |
| 20 days ago | Failed - the connection was refused or dropped | — |
| 22 days ago | Handshake completed | 792 ms |
| 24 days ago | Failed - the connection was refused or dropped | — |
| 26 days ago | Handshake completed | 2.21 s |
| 27 days ago | Handshake completed | 730 ms |
| 28 days ago | Handshake completed | 689 ms |
| 29 days ago | Handshake completed | 718 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 29.
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 Liepin Jobs and makes no claim about it beyond what these checks measured.