Remote MCP · Endpoint

Lingshu Solver MCP server

No. Lingshu Solver answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://hongchenlingjing.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.genesis-plan/lingshu-solver
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
789 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deterministic MCP solver for real equation systems (<=6 vars), Krawczyk-certified.
Listing
From the official MCP registry (active).
Recent checks of Lingshu Solver
CheckedResultHandshake
2 hours agoHandshake completed789 ms
2 days agoHandshake completed833 ms
4 days agoHandshake completed801 ms
6 days agoHandshake completed878 ms
8 days agoHandshake completed846 ms
10 days agoHandshake completed843 ms
12 days agoHandshake completed811 ms
14 days agoHandshake completed760 ms
15 days agoHandshake completed779 ms
16 days agoHandshake completed781 ms
18 days agoHandshake completed751 ms
20 days agoHandshake completed865 ms
22 days agoHandshake completed790 ms
23 days agoHandshake completed807 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 Lingshu Solver and makes no claim about it beyond what these checks measured.