io.github.MerakOsiris/memoryguard
MemoryGuard
Is the MemoryGuard MCP server down? No. It is up and needs args, probed 2026-10-31.
Local-first governed MCP memory backend for coding agents.
needs args probed 2026-11-14 · unchanged since 2026-10-31
MCP error -32000: Connection closed
usage: memoryguard [-h] [--version]
{audit,open,explain,plan,apply,verify,undo,source,scan,import,doctor,- Run it
- uvx agent-memguard@0.7.15 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/MerakOsiris/memoryguard
- Website
- https://github.com/MerakOsiris/memoryguard
- Registry
- active, updated 2026-09-30 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.MayankTalwar0/startup-finance-metrics · needs mcp<2
- io.github.Maytrella007/protonlite · needs args
- KrystalView Analytics io.github.McSlaine/krystalview · needs mcp<2
- Memphora io.github.Memphora/memphora · crashed on start
- PraisonAI io.github.MervinPraison/praisonai · needs env
- TG multi-account MCP io.github.Mesteriis/tg-account-mcp · not probed
- MCAI Knowledge Base io.github.Meta-consciousness-AI/mcai-knowledge · crashed on start
- io.github.Mibayy/token-savior · alive
Servers that mention memoryguard or governed or backend.
- MemoryGuard io.github.irisxc4/memoryguard · needs args
- ai.duvera/gateway · alive
- Elaichi ai.elaichi/mcp · needs auth
- ai.getvda/observable-backend-stack-generator · newer protocol
- Kumbuka ai.kumbuka/kumbuka-server · needs auth
- ai.matih/mcp · needs auth
- ai.multi-turn/enacta · no DNS
- n3tz Atlas ai.n3tz/atlas · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-31 07:37 | needs args | ||||
| 2026-10-17 06:18 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server needs command line arguments that the registry entry does not list. Add them to the package arguments in the registry entry.