MCP server list / VaultCrux Memory Core
Remote MCP for VaultCrux Memory Core queries, snapshots, freshness, audits, and contradictions.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 637 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 646 ms.
- Address
- https://api.vaultcrux.com/
memory-core/ mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.CueCrux/
vaultcrux-memory-core - Transport
- streamable HTTP
streamable-http - Host
api.vaultcrux.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- vaultcrux-memory-core
- Version:
- v0.3.4+sha.2db2250f556f
- MCP features it lists:
- tools
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 501 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,009 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 628 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 646 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.