mcpbeat Sign in

ContextDB Customer Memory MCP Server

answering

ContextDB Customer Memory is answering right now. Last checked 7 min ago.

Customer memory with recall, confirmation, forgetting, and pre-action evidence checks.

Uptime history 24 days of history · worst day 96%
24 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
450 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check ContextDB Customer Memory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add contextdb-memory --transport http https://api.contextdb.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "contextdb-memory": {
      "url": "https://api.contextdb.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.contextdb-memory]
url = "https://api.contextdb.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "contextdb-memory": {
      "url": "https://api.contextdb.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "contextdb-memory": {
      "url": "https://api.contextdb.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.contextdb.ai/mcp streamable-http sign-in 423 ms 7 min ago

Alternatives to ContextDB Customer Memory

same job, measured the same way
Audrey
by evilander

Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks.

103 installs/wk local only
Feason Context
by feason-com

Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.

answering
Engram
by tstockham96

Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

109 installs/wk local only
Evident Reviews
by evidentagents

Consumer reviews with private receipts, optional ratings and one-step consumer confirmation.

16 tools answering
Nahuali
by arakiss

Trust-aware agent memory with evidence-backed recall, self-inspection, and audit history.

local only
inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
by dancenitra

Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.

6 566 installs/wk local only
Instinct
by yakuphanycl

Self-learning memory for AI coding agents with pattern detection and confidence scoring.

1 installs/wk local only
ContextDB Memory
by mikhailbovt

Local-first durable AI memory with policy-bound recall and a typed project graph.

local only

ContextDB Customer Memory — questions

Answers built from our own checks of this server.

Why is there no tool list for ContextDB Customer Memory?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is ContextDB Customer Memory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 450 ms. The bar chart above shows every period we have measured.
How do I connect ContextDB Customer Memory?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to ContextDB Customer Memory?
No API key is involved. ContextDB Customer Memory answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is ContextDB Customer Memory?
It answers our handshake in 450 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.