Remote MCP · Endpoint

一人行 SoloTeam MCP MCP server

No. 一人行 SoloTeam MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://soloteam.com.cn/mcp

The last check completed an MCP handshake.

Registry name
cn.com.soloteam/soloteam
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
828 ms
Tools exposed
11 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
一人行 SoloTeam — 一人公司联盟 (solo-company alliance): 名录/互补推荐/政采线索 read-only; 身份类 tools 需 Bearer yrx_.
Listing
From the official MCP registry (active).
Recent checks of 一人行 SoloTeam MCP
CheckedResultHandshake
1 hour agoHandshake completed828 ms
2 days agoHandshake completed2.24 s
5 days agoHandshake completed800 ms
7 days agoHandshake completed745 ms
9 days agoHandshake completed2.28 s
11 days agoHandshake completed865 ms
13 days agoHandshake completed747 ms
15 days agoHandshake completed928 ms
17 days agoHandshake completed1.96 s
18 days agoHandshake completed734 ms
20 days agoHandshake completed3.56 s
21 days agoHandshake completed739 ms
23 days agoHandshake completed815 ms
25 days agoFailed - the hostname does not resolve—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 一人行 SoloTeam MCP and makes no claim about it beyond what these checks measured.