MCP.Market

Zekra MCP server

online · 100% uptime
by fadymondy·io.github.fadymondy/zekra·v0.1.0

Long-term memory and a knowledge graph for AI agents: recall, notes, secrets and data sources.

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

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Zekra yet.

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

Zekra tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 702ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Zekra compares

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

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
529 ms
faster than 28% of 30,031 servers

Install Zekra in Claude Code, Cursor or VS Code

claude mcp add --transport http zekra https://mcp.zekra.dev
Add to Cursor

What the publisher says

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

Zekra

ذكرى — shared long-term memory for AI agents. What one session learns, the next one already knows.

Zekra is a memory service that any agent (Claude Code, Codex, Gemini, Cursor, your own fleet) reaches over MCP. It stores what agents and people learn, deduplicates and updates it on write, and returns exactly the right memory on recall — with citations — so nobody re-derives what is already known.

  • Landing: https://zekra.dev
  • Console + API + MCP: https://app.zekra.dev
  • CLI: fadymondy/zekra-cli

Documentation

Full docs at https://zekra.dev/en/docs (source: docs/):

Security · Self-hosting

  • Introduction and Quickstart
  • MCP server: tool reference and client setup
  • CLI: the zekra command and the Claude Code plugin
  • REST API: endpoints, errors, events, TypeScript client
  • Data sources · Capture hook ·

What it does

a salience nudge, reranking, and 1-hop entity expansion. A write-decision step (ADD / UPDATE / INVALIDATE / NOOP) updates contradicted facts instead of duplicating them. Nothing is hard-deleted: forget soft-invalidates and history stays queryable.

  • Retain / recall — hybrid retrieval: dense vectors + multilingual BM25 fused with RRF,

tokens (cbt_…) enforced server-side.

  • Many brains — one namespace per project or team, with per-agent grants and access

traverse / neighbors / path / ontology queries and a graph "spine".

  • Knowledge graph — entities and typed relations extracted from memories, with

pull external content, chunk it and retain it through the same write pipeline. See Data sources.

  • Data sources — connectors (text, markdown, crawler, github, sql, webhook)

graph / retain as tools and answers with citations and an auditable trace.

  • Chat with a brain — a tool-calling agent that uses the brain's own recall / search /
  • Knowledge gaps, secrets vault, activity log — plus a web console to manage it all.
  • Tiers — Redis L1 working-memory cache, hot Postgres tier, object-store cold tier.

Connect an agent

curl -fsSL https://app.zekra.dev/install.sh | sh     # installs the `zekra` CLI
zekra auth login --token <cbt_…>
zekra mcp:install claude-code                        # or claude-desktop | codex | gemini | cursor

MCP tools include memoryretain, memoryrecall, memoryget, memoryforget, memoryshare, memoryedit, graph, memorygaps, brain (list, grants, tokens, chat), secret and datasource_*. Full reference: MCP server · contracts: contracts/tools.md.

Architecture

Zekra is a togo app built from plugins:

Shortened. The full README is on GitHub.

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

Zekra: common questions

Is Zekra MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Zekra safety report
How do I install Zekra?
It runs remotely at mcp.zekra.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Zekra need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Zekra maintained?
The last commit was 24 days ago (2026-10-11). The latest release is v0.1.0.
Is Zekra up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Zekra?
Servers from other publishers that do the same job: Codebase Memory MCP server, Neo4j Memory MCP server and Nautilus Compass Memory MCP server.
How does Zekra compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 529 ms (faster than 28% of 30,031 servers). Full comparison.

Alternatives to Zekra

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

  • Codebase Memory
    Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
    C
  • Neo4j Memory
    MCP Neo4j Knowledge Graph Memory Server
    A
  • Nautilus Compass Memory
    Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.
    B
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A