haki

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.GetHaki/haki and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 8 Sept 2026. Not supplied by the maker.

• haki_context

  Recall the project's memory (decisions, conventions, preferences) relevant to a task. Call BEFORE planning or editing code. Returns a ready-to-inject block with dates and sources, the trace_id

• haki_capture

  Memorize a durable project fact: technical decision, convention, resolved error. Call at the END of a task. Never memorize secrets, tokens or ephemeral data. Consolidation is synchronous in de

• haki_inspect

  Inspect the trace of a haki_context call: which facts were included, excluded or blocked, and why (reason_code). Provenance proof of the served memory.

• haki_forget

  Forget the configured subject's memory in this project. mode='disable' (reversible, facts move to disabled) or 'delete' (real erasure: facts, embeddings, events, traces). Returns the erasure r

• haki_correct

  Correct the memory from inside the conversation (M10). rating='incorrect' with a fact_id moves that fact to 'disputed': haki_context will never recall it again. rating='useful'/'irrelevant' lo

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.