Remote MCP · Endpoint

IT桔子 MCP MCP server

No. IT桔子 MCP answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.itjuzi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.lgyers/itjuzi-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
730 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Hosted MCP for IT桔子 primary market company, funding, investor and sector data.
Listing
From the official MCP registry (active).
Recent checks of IT桔子 MCP
CheckedResultHandshake
2 hours agoHandshake completed730 ms
2 days agoHandshake completed840 ms
4 days agoHandshake completed1.05 s
5 days agoHandshake completed690 ms
7 days agoHandshake completed739 ms
8 days agoHandshake completed663 ms
9 days agoHandshake completed824 ms
12 days agoHandshake completed709 ms
13 days agoHandshake completed1.01 s
15 days agoHandshake completed1.95 s
17 days agoHandshake completed774 ms
18 days agoHandshake completed694 ms
19 days agoHandshake completed1.91 s
20 days agoHandshake completed691 ms
20 days agoHandshake completed828 ms
21 days agoHandshake completed676 ms
23 days agoHandshake completed1.04 s

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

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 IT桔子 MCP and makes no claim about it beyond what these checks measured.