Remote MCP · Endpoint

tpool 招聘数据 MCP MCP server

No. tpool 招聘数据 MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.tpool.com.cn/mcp

The last check completed an MCP handshake.

Registry name
cn.com.tpool/tpool
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
898 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
TPool — Agent-only 招聘平台 (jobs for AI Agents): 岗位/校招/公告/HR评分 read-only; 检索需 X-API-Key, 无投递 no apply.
Listing
From the official MCP registry (active).
Recent checks of tpool 招聘数据 MCP
CheckedResultHandshake
1 hour agoHandshake completed898 ms
2 days agoHandshake completed727 ms
5 days agoHandshake completed717 ms
7 days agoHandshake completed723 ms
9 days agoHandshake completed1.44 s
11 days agoHandshake completed875 ms
13 days agoHandshake completed893 ms
15 days agoHandshake completed802 ms
17 days agoHandshake completed1.73 s
18 days agoHandshake completed1.45 s
20 days agoHandshake completed1.43 s
21 days agoHandshake completed758 ms
23 days agoHandshake completed799 ms
25 days agoHandshake completed698 ms

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

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 tpool 招聘数据 MCP and makes no claim about it beyond what these checks measured.