mcpbeat Sign in

Zekra MCP Server

answering

Zekra is answering right now. Last checked 14 min ago. Last commit 14 Oct 2026.

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

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
208 ms
Response time
average over 24h
0
Stars
last commit 14 Oct 2026

What the code does

We read the source, 1 d ago · rules ccca72095570

Capabilities

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.

    execFile(file, args, { timeout: timeoutMs, encoding: "utf8" }, (err, stdout, stderr) => {
const has = (rel) => fs.existsSync(path.join(__dirname, rel));
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Runs an external command infra/ocr/app.py:273
            p = subprocess.run(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

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.

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 14 min ago.

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

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://mcp.zekra.dev streamable-http sign-in 178 ms 14 min ago

Alternatives to Zekra

same job, measured the same way
Alaya MCP
by securityronin

Local memory engine for AI agents with knowledge graphs, forgetting, and semantic recall

51 installs/wk local only
Privacyscrubber MCP
by moxno

Zero-Trust PII & secrets sanitizer for AI agents with in-memory local redaction.

1 224 installs/wk local only
Wundervault MCP
by wundervault

Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model

62 installs/wk local only
Changegamer
by beneb89

Agent-first resource directory for AI agents: protocols, security, RAG, memory, evals, and more.

14 tools answering
Weasley DeepMind
by potatohoney-p

Secure, fragment-based long-term memory for MCP-compatible AI agents.

69 installs/wk local only
Agent Memory
by xchucx

Git-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe.

91 installs/wk local only
Lattice: CVE, MITRE ATT&CK and detection graph for security agents
by namiq

CVE, KEV, MITRE ATT&CK, CWE and detection graph for AI agents; every link names its source.

7 tools answering
seekrit (local crypto plane)
by seekrit

Zero-knowledge secrets manager — local crypto-plane MCP server: decrypts and injects secrets.

78 installs/wk local only

Zekra — questions

Answers built from our own checks of this server.

Why is there no tool list for Zekra?
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 Zekra working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 208 ms. The bar chart above shows every period we have measured.
How do I connect Zekra?
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 Zekra?
No API key is involved. Zekra 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 Zekra?
It answers our handshake in 208 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Zekra open source?
Yes — it is published under the AGPL-3.0 licence, written in TypeScript, 0 stars on GitHub and 5 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.