Persistent AI memory for Claude Code, Cursor, Copilot, Windsurf, Cline & Zed. Your AI remembers every lesson, fix, and architecture decision — across sessions, IDEs, and model upgrades. Quality-aware recall beats raw BM25 keyword search by **+33% Precision@1** on our published benchmark. Features causal root-cause analysis (causal_trace), failure prediction (brain_predict), git-ambient learning (brain_from_git), shared Team Brain, and Memory Crystals. BM25+ search in 11 languages. **122 tools. Free tier. GDPR, EU-hosted on German servers.** Zero-config: sign in once at [cachly.dev/setup-ai](https://cachly.dev/setup-ai) — your Brain instance is provisioned automatically. No credit card required.
cachly AI Brain is a remote MCP server published at mcp.cachly.dev. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 286 ms, placing it among the faster endpoints. It exposes a broad tool surface of 27 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
semantic_search — Overlaps with smart_recall in semantic search functionalitybrain_predict — References CKG/Redis without defining acronymslearn_from_attempts — Unclear 'grund' parameter definitioncausal_trace — No explicit error handling for missing prior learningcachly_tool — Generic name with no specific use case clarificationRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/cachly-dev-cachly-mcp)<a href="https://mcpmetrics.io/servers/cachly-dev-cachly-mcp"><img src="https://mcpmetrics.io/badge/cachly-dev/cachly-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 11:20:19 | Legacy | 400 | 216 | 200 | 209 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 281 | 200 | 286 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 506 | 200 | 501 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 130 | 200 | 119 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 167 | 200 | 161 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 400 | 337 | 200 | 344 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 409 | 401 | 431 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.