AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP unreviewed MIT Self-run

GZMO

mcp-maximilianwruhs-cyber-gzmo · by maximilianwruhs-cyber

Sovereign curated memory for coding agents — local SQLite, honeypot gate, supersession chains — MCP for Cursor & Pi

↗ Website ↗ Repository
— No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add mcp-maximilianwruhs-cyber-gzmo

Open-source listing — not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

  • • Prompt-injection patterns
  • • Secret / credential exfiltration
  • • Dangerous shell & filesystem operations
  • • Untrusted network calls
  • • Known-malicious package signatures
  • high Pipes remote content directly into a shell (remote code execution).

What it can access

  • ● Network access Used
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Reliability & compatibility

— Not yet reviewed
0 installs to date
— no reviews yet
● 13d ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of GZMO? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

GZMO

Sovereign, curated long-term memory for coding agents — honeypot quality gate, supersession chains, local SQLite — exposed as MCP for Cursor and Pi.

Not another cloud notebook. Not Mem0.

Install (under 10 minutes)

1. Install binary + ~/.gzmo + wire MCP

curl -fsSL https://raw.githubusercontent.com/maximilianwruhs-cyber/GZMO/main/scripts/install-gzmo.sh | bash

Writes SQLite-only ~/.gzmo/ (no LAN) and merges gzmo-memory into Cursor / Pi mcp.json.

2. Verify on the machine

# From a clone (or after install):
./scripts/product-stranger-path.sh   # cold product verify checklist
./scripts/mcp-attach-check.sh        # Cursor/Pi point at ~/.gzmo (not CT101)
# Optional feel-it (needs local LLM, e.g. Prime :8000):
./scripts/product-first-fact.sh
# Production gate (exit 0 = PRODUCT GREEN):
./scripts/product-readiness-gate.sh

3. Attach in the agent

In Cursor or Pi, call:

  1. gzmo_memory_status — vault path should be under ~/.gzmo/
  2. gzmo_memory_search — search your local vault

Full guide: [docs/PRODUCTMCP.md](docs/PRODUCTMCP.md).

Pi package (optional UX)

pi install npm:gzmo-pi   # or: pi install git:github.com/maximilianwruhs-cyber/gzmo-pi

In Pi: /gzmo setup → /reload → gzmo_memory_status. Package: gzmo-pi. Living Redis/Neo4j/Qdrant is not required for laptop product.

From source

cargo build --release -p gzmo-cli
GZMO_BIN=./target/release/gzmo ./scripts/install-gzmo.sh

What you get

| | | |---|---| | Local vault | ~/.gzmo/data/vault.db — facts stay on disk | | Honeypot curation | Quality-gated recall, not a raw dump | | Supersession chains | gzmo_memory_chain shows how facts were replaced | | MCP stdio | Works with Cursor and Pi | | FTS-first | Offline by default; optional embeddings later |

MCP tools

| Tool | Purpose | |------|---------| | gzmo_memory_status | Vault path, fact counts, session | | gzmo_memory_search | Search honeypot / vault | | gzmo_memory_turn_start | Clear session scratch | | gzmo_memory_recall_pull | Pull scratch block | | gzmo_memory_chain | Provenance / supersession chain | | gzmo_memory_profile | Cached operator profile | | gzmo_wiki_search | Wiki layer (if enabled) |

Operator-only probes (gzmo_ops_health, gzmo_discovery_status) require GZMO_OPS_MCP=1.

Non-goals (v1)

  • Multi-host living topologies and discovery / mentor pedagogy as install steps
  • Cloud-hosted memory SaaS — use Mem0 MCP if you want that
  • Overnight gzmo serve, Redis, Qdrant, or Neo4j required for first attach
  • SEIP / Foundry-class platforms inside this product surface

If a change does not help a stranger get gzmo_memory_search working in under 10 minutes, it is not product.

Optional next steps

After MCP works you can enable [embeddings] against any OpenAI-compatible local URL. Redis/Qdrant compose and overnight metabolism are advanced — see [docs/PRODUCTMCP.md](docs/PRODUCTMCP.md#advanced-phase-2--deferred).

Docs

| Doc | Audience | |-----|----------| | [docs/PRODUCTMCP.md](docs/PRODUCTMCP.md) | Product install + verify | | [docs/README.md](docs/README.md) | Operator / architecture index | | [CONTRIBUTING.md](CONTRIBUTING.md) | Dev setup |

License

[MIT](LICENSE)

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Databases