Griasa runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Nov 2026.
Local-first Mac meeting memory: open promises, people, next-meeting briefs. Read-only.
What the code does
We read the source, 3 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
let process = Process()
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.
let process = Process()
with open(os.path.join(target, name), "w") as handle:
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Griasa and you get told the day something new turns up.
Alternatives to Griasa
same job, measured the same wayRead-only audit of any local service business, Open Service Profile conformance first.
Your recorded Mac meetings in Claude: search, promises with owners, follow-ups. Local, read-only.
Local-first ambient memory for your Mac — pages, meetings, notes, encrypted on-device.
Local-first, read-only MCP server for evidence-backed repository memory.
Local-first AI memory engine — 4-tier memory, people graph, Bayesian beliefs. Encrypted, 62µs.
Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt.
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP.
Local-first memory of how you write: style profile and real reply examples from your chat exports
Griasa — questions
Answers built from our own checks of this server.