MCP.Market

Memors MCP server

by kKEo·io.github.kKEo/memors·v1.6.5

Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Memors yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Memors tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Memors compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 802 Databases servers

Release history: 4 versions in the registry since 2026-10-11, latest 2026-11-02, typically one every 4 days.

Install Memors in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Memors repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.kKEo/memors -->

memors-mcp

A local MCP server that gives agents a measurable, explainable knowledge base: one Go binary, no cloud, no CGo, one SQLite file per knowledge base. Documents and facts go in with provenance; searches come back as one ranked list from four retrieval arms, each result with its address, trust and a reason for its rank. A human reads the same knowledge base from the terminal or as exported markdown.

It began as a Go rewrite of obra/private-journal-mcp and was rebuilt from scratch as a knowledge base in 2026-10. Version 1.0 fixes the contract: tool names and parameters, the memo:// addresses, the explain fields and the export format. How search decides is written down in docs/architecture.md; the plan for the research layers (graph, compaction, web UI) is docs/roadmap.md; the research behind it is docs/knowledge-base-sota.md.

What it does

Claude (or any MCP client) gets ten tools over one knowledge base:

On macOS, the optional menu-bar app MemoRS Tray (tray/, a separate binary; the only part built with cgo) shows the clients connected to each memors-mcp serve --http server, opens a server's Live page in a window, and starts and stops servers. Its setup assistant downloads, verifies and installs memors-mcp from the GitHub releases and sets up a first knowledge base, and its settings window covers the rest (launch at login, servers, embedding model). See docs/guide/user/menu-bar.md.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Memors: common questions

Is Memors MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Memors safety report
Does Memors need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Memors maintained?
The last commit was 24 days ago (2026-10-11). The latest release is v1.6.5.
What can I use instead of Memors?
Servers from other publishers that do the same job: Titen Memory MCP server, sqlite-graph-memory MCP server and AlphaFold Sovereign MCP server.

Alternatives to Memors

Same job from other publishers: the closest match first, then the best rated.

  • Titen Memory
    Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
    B
  • sqlite-graph-memory
    Recall over your markdown notes: vector search plus your [[wikilinks]] as a graph, in SQLite.
    A
  • AlphaFold Sovereign MCP
    MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph
    A
  • Faostat
    UN FAOSTAT global food & agriculture statistics over a local SQLite mirror, via MCP.
    A
  • Tinycontext
    Token-light local memory with SQLite hybrid retrieval for MCP agents.
    B