Remote MCP · Endpoint

VaultCrux Memory Core MCP server

No. VaultCrux Memory Core answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.vaultcrux.com/memory-core/mcp

The last check completed an MCP handshake.

Registry name
io.github.CueCrux/vaultcrux-memory-core
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
388 ms
Tools exposed
75 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
Repository
https://github.com/CueCrux/VaultCrux
Listing
From the official MCP registry (active).
Recent checks of VaultCrux Memory Core
CheckedResultHandshake
2 hours agoHandshake completed388 ms
2 days agoHandshake completed369 ms
4 days agoHandshake completed404 ms
5 days agoHandshake completed366 ms
7 days agoHandshake completed399 ms
8 days agoHandshake completed400 ms
9 days agoHandshake completed405 ms
12 days agoHandshake completed370 ms
13 days agoHandshake completed406 ms
15 days agoHandshake completed401 ms
17 days agoHandshake completed401 ms
18 days agoHandshake completed401 ms
19 days agoHandshake completed369 ms
20 days agoHandshake completed405 ms
20 days agoHandshake completed382 ms
21 days agoHandshake completed430 ms
23 days agoHandshake completed390 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.

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 VaultCrux Memory Core and makes no claim about it beyond what these checks measured.