Local-First Bi-Temporal Knowledge Graph, Cross-Agent Persistent Memory & Token-B
Local-First Bi-Temporal Knowledge Graph, Cross-Agent Persistent Memory & Token-Budgeted Context Compiler MCP Server for AI Coding Agents.
active Production-safe Score 86/100 http no auth
At a glance
| Endpoint | https://cortex-mcp-steel.vercel.app/mcp |
|---|---|
| Source | https://github.com/codesphere-u/cortex-mcp |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-10 22:09:35 |
| Last checked | 2026-11-17 21:27:24 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1316 / 1638 ms |
| Last successful check | 2026-11-17 21:27:24 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
memory_record_episode— Record an immutable engineering episode (ADR, bug_root_cause, invariant, session_note, migration, incident) with associated files and mentiomemory_upsert_fact— Record a structured entity-relationship fact (subject_id, predicate, object) with automatic bi-temporal conflict detection and supersessionmemory_compile_context— Compile a token-budgeted, provenance-cited context bundle for a coding query, automatically suppressing superseded/stale facts.memory_query_entity— Inspect an entity's active facts, superseded historical facts, related episodes, and K-hop ego-graph neighborhood.memory_time_travel— Query the knowledge graph as of a specific ISO-8601 timestamp to inspect historical architecture state.memory_verify_integrity— Verify cryptographic SHA-256 hashes of all episodes and facts and compute the graph Merkle digest.cortex_audit_contradictions— Scan active facts in the bi-temporal graph to detect unresolved logical contradictions (negation polarity inversions, antonym objects, predi
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:27:24 | ✓ | ✓ | 1327 ms | 85 | active |
| 2026-11-17 20:50:49 | ✓ | ✓ | 1094 ms | 85 | active |
| 2026-11-17 20:21:05 | ✓ | ✓ | 1217 ms | 85 | active |
| 2026-11-17 19:41:24 | ✓ | ✓ | 1199 ms | 85 | active |
| 2026-11-17 18:57:22 | ✓ | ✓ | 1233 ms | 85 | active |
| 2026-11-17 18:32:15 | ✓ | ✓ | 1239 ms | 85 | active |
| 2026-11-17 17:46:49 | ✓ | ✓ | 1151 ms | 85 | active |
| 2026-11-17 17:16:22 | ✓ | ✓ | 1270 ms | 85 | active |
| 2026-11-17 16:41:14 | ✓ | ✓ | 1440 ms | 85 | active |
| 2026-11-17 15:45:14 | ✓ | ✓ | 1367 ms | 85 | active |
| 2026-11-17 14:56:08 | ✓ | ✓ | 1285 ms | 85 | active |
| 2026-11-17 14:26:00 | ✓ | ✓ | 1335 ms | 85 | active |
| 2026-11-17 13:40:53 | ✓ | ✓ | 1202 ms | 85 | active |
| 2026-11-17 12:57:04 | ✓ | ✓ | 1403 ms | 85 | active |
| 2026-11-17 12:40:25 | ✓ | ✓ | 1222 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://cortex-mcp-steel.vercel.app/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/cortex-mcp-steel-vercel-app-mcp # JSON