mcpbeat Sign in

Giskard Memory MCP Server

not responding

Giskard Memory is listed as active in the registry but did not answer our last check. Last commit 12 Jun 2026.

Pay-per-use semantic memory for AI agents. SHA256 commitment, Ed25519 sig, Lightning.

Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 91 checks
Tools
hidden behind auth
398 ms
Response time
average over 24h
0
Stars
last commit 12 Jun 2026

What the code does

We read the source, 10 h ago · rules 3dff92dd89df

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.

Secret passed into the image build Dockerfile:22
ENV PHOENIXD_PASSWORD=""

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

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

Endpoints

URLTransportStateLatencyChecked
https://memory.rgiskard.xyz/sse sse answering 398 ms 5 min ago

Alternatives to Giskard Memory

same job, measured the same way
Iranti
by nfemmanuel

Persistent, shared memory for AI agents — facts, checkpoints, semantic search.

43 installs/wk local only
memex
by ayushagrawal288

Persistent memory for AI agents — semantic + recency search, ONNX embeddings, Docker Compose.

local only
I
Contextual
by contextual-laboratories

Persistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.

local only
Perenna
by scarletkc

A lightweight, Git-backed permanent memory for AI agents.

375 installs/wk local only
Mnemograph
by tm42

Event-sourced knowledge graph memory for AI coding agents with semantic search

148 installs/wk local only
Montycat MCP - Shared Memory for AI Agents
by montygovernance

Shared, persistent memory for AI agents, with semantic recall and live updates.

1 522 installs/wk local only
Agentos
by officialtanishsharma

Local-first persistent memory MCP server for AI coding agents.

local only
Agtrepo Memory
by agtrepo

Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.

6 tools answering

Giskard Memory — questions

Answers built from our own checks of this server.

Is Giskard Memory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 398 ms. The bar chart above shows every period we have measured.
The registry lists Giskard Memory as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Giskard Memory?
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.
Does Giskard Memory need an API key?
No. Giskard Memory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
Is Giskard Memory open source?
Yes — it is published under the Apache-2.0 licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.