Remote MCP · Endpoint

xmp4 — Semantic code knowledge for your stack MCP server

No. xmp4 — Semantic code knowledge for your stack answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.example4.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.example4/xmp4
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
294 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.
Listing
From the official MCP registry (active).
Recent checks of xmp4 — Semantic code knowledge for your stack
CheckedResultHandshake
10 hours agoHandshake completed294 ms
2 days agoHandshake completed296 ms
4 days agoHandshake completed289 ms
5 days agoHandshake completed293 ms
7 days agoHandshake completed298 ms
8 days agoHandshake completed292 ms
9 days agoHandshake completed289 ms
12 days agoHandshake completed293 ms
13 days agoHandshake completed376 ms
15 days agoHandshake completed297 ms
16 days agoHandshake completed291 ms
17 days agoHandshake completed292 ms
18 days agoHandshake completed293 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed291 ms
21 days agoHandshake completed286 ms
23 days agoHandshake completed288 ms

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 xmp4 — Semantic code knowledge for your stack and makes no claim about it beyond what these checks measured.