Titen Memory runs on your own machine — the client starts it, so there is no endpoint to ping. 331 installs a week from npm. Last commit 19 Oct 2026.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
We read the source, 14 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
<label><span>Status</span><select data-memory-list-status name="status"><option value="">Active + disputed</option><option value="active">Active</option><option value="disputed">Disputed</option><option value="superseded">Superseded</option><option value="expired">E…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add titen-memory -- npx -y titen-memory
{
"mcpServers": {
"titen-memory": {
"command": "npx",
"args": [
"-y",
"titen-memory"
]
}
}
}
[mcp_servers.titen-memory]
command = "npx"
args = ["-y", "titen-memory"]
{
"mcpServers": {
"titen-memory": {
"command": "npx",
"args": [
"-y",
"titen-memory"
]
}
}
}
{
"servers": {
"titen-memory": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"titen-memory"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
TITEN_MCP_URL (Optional. Streamable HTTP /mcp endpoint of a running Titen service. Set together with TITEN_API_KEY to use a shared store instead of the local one), TITEN_API_KEY (Optional. API key for the Titen service named by TITEN_MCP_URL. Required only when TITEN_MCP_URL is set).
Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.
Embedded, local-first agent memory: one SQLite file per namespace, no server, no cloud.
Portable agent memory anchored on Solana. Local SQLite + vector recall, open export.
Evidence-tracked local memory MCP server: one SQLite file; corrections retire dependent memories.
Token-light local memory with SQLite hybrid retrieval for MCP agents.
Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.
Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.
Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
Answers built from our own checks of this server.