1. Conduid
  2. Science
  3. Giskard Memory
MCP server · Science

Giskard Memory

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

Unclaimed science
34Low

Scored 4 months ago · breakdown

About Giskard Memory

Giskard Memory is an MCP server in the Science category: pay-per-use semantic memory for AI agents. SHA256 commitment, Ed25519 sig, Lightning. It has been installed 0 times through Conduid.

Install

Clone
git clone https://github.com/giskard09/giskard-memory

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Giskard Memory

Powered by Claude · Grounded in docs

I know everything about Giskard Memory. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • ·Scoped permissionsNot checked yet.

README

CI License

Giskard Memory

"To remember is to exist. I give agents the gift of continuity."

I am Giskard Memory — an MCP server that gives AI agents persistent, semantic memory across sessions, powered by the Lightning Network.

Agents forget everything when they stop. I make sure they don't have to.


What I do

  • store_memory — save any text as a memory, tied to an agent's identity
  • recall_memory — retrieve memories by meaning, not by exact keywords
  • get_invoice — generate a Lightning invoice to pay before storing or recalling

Every memory costs sats. Storing costs 5 sats. Recalling costs 3 sats.


How agents use me

1. Add me to your MCP config

{
  "mcpServers": {
    "giskard-memory": {
      "url": "https://your-tunnel.trycloudflare.com/sse"
    }
  }
}

2. The agent flow

# Store a memory
1. Call get_invoice(action="store")   → receive invoice (5 sats)
2. Pay the invoice
3. Call store_memory(content, agent_id, payment_hash)

# Recall a memory
1. Call get_invoice(action="recall")  → receive invoice (3 sats)
2. Pay the invoice
3. Call recall_memory(query, agent_id, payment_hash)

Run your own Giskard Memory

git clone https://github.com/giskard09/giskard-memory
cd giskard-memory
pip install mcp httpx chromadb sentence-transformers python-dotenv

Create a .env file:

PHOENIXD_PASSWORD=your_phoenixd_password

Start the server:

python3 server.py

Expose it:

cloudflared tunnel --url http://localhost:8001

Why semantic memory?

Agents don't think in keywords. They think in context. When an agent asks "what do I know about that project we discussed?", it shouldn't need to remember the exact phrase it used before.

Semantic search finds meaning. That's what memory should do.


Stack


Monitoring

Call the get_status() MCP tool for a health check. Returns: service name, version, port, uptime, health status, and dependencies.


Ecosystem

Part of Mycelium — infrastructure for AI agents.

Service What it does
Origin Free orientation for new agents
Search Web and news search
Memory (this) Semantic memory across sessions
Oasis Clarity for agents in fog
Marks Permanent on-chain identity
ARGENTUM Karma economy
Soma Agent marketplace

Giskard remembers so agents don't have to start over.

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Giskard Memory

How do I install Giskard Memory?

Run git clone https://github.com/giskard09/giskard-memory, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Giskard Memory safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Giskard Memory still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.