Dense Mem
UnclaimedSelf-hosted AI agent memory server with MCP, evidence provenance, typed claims, conflict detection, embeddings, recall, PostgreSQL, and pgvector
Set up this server
More in Search & Web
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
14 of 14 tools
Documented tools (14)
From project documentation. A server handshake does not verify each tool’s description or behavior.
correct_relationship
Production
eval_list_knowledge_refs
Evaluation harness
eval_run_dream_cycle
Evaluation harness
eval_run_recall_case
Evaluation harness
export_memory_pack
Production
get_dream
Production
get_submission_status
Both
list_dreams
Production
recall_memory
Production
remember
Both
resolve_dream_feedback
Production
retract_evidence
Production
submit_recall_session_feedback
Production
trace_memory
Production
Tool change history
FAQ
Questions about Dense Mem MCP Server
- How do I connect Dense Mem MCP Server to Claude?
- The project does not publish a launch command that MCPVault could verify. Open the repository linked on this page for its install steps; the listing names Claude Code, Cursor and Claude Desktop as compatible clients.
- Is Dense Mem MCP Server free?
- The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Dense Mem MCP Server do?
- Dense Mem MCP Server documents 14 tools to the agent, including correct_relationship, eval_list_knowledge_refs, eval_run_dream_cycle. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.