Remote MCP · Endpoint

xmp4 — Semantic code knowledge for your stack MCP server

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

UpLast checked 2 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
292 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.
Website
https://example4.ai/
Repository
https://github.com/0ics-srls/lsai-xmp4.public
Listing
From the official MCP registry (active).
Recent checks of xmp4 — Semantic code knowledge for your stack
CheckedResultHandshake
2 hours agoHandshake completed292 ms
1 day agoHandshake completed363 ms
3 days agoHandshake completed290 ms
3 days agoHandshake completed291 ms
4 days agoHandshake completed301 ms
5 days agoHandshake completed297 ms
7 days agoHandshake completed303 ms
10 days agoHandshake completed292 ms
12 days agoHandshake completed295 ms
14 days agoHandshake completed290 ms
17 days agoHandshake completed295 ms
19 days agoHandshake completed388 ms
21 days agoHandshake completed294 ms
23 days agoHandshake completed296 ms
25 days agoHandshake completed289 ms
26 days agoHandshake completed293 ms
28 days agoHandshake completed298 ms
29 days agoHandshake completed292 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.

xmp4 — Semantic code knowledge for your stack MCP server - status, uptime and latency - Glide