Remote MCP · Endpoint

io.github.aixingzhe/sagelib MCP server

No. io.github.aixingzhe/sagelib answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://www.sagelib.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.aixingzhe/sagelib
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
680 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
List, compare, and call 68 LLMs with live pricing through one Chinese API gateway.
Listing
From the official MCP registry (active).
Recent checks of io.github.aixingzhe/sagelib
CheckedResultHandshake
10 hours agoHandshake completed680 ms
4 days agoHandshake completed702 ms
7 days agoHandshake completed724 ms

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

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 io.github.aixingzhe/sagelib and makes no claim about it beyond what these checks measured.