mcpbeat

Giskard Memory MCP Server

io.github.giskard09/memory
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 43 hours of history · worst hour 0%
43 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
427 ms
Response time
average over 24h
0
Stars
last commit 12 Jun 2026

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 427 ms 5 min ago

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 427 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.