io.github.GetHaki/haki
REMOTE · API.GETHAKI.SPACE · SCANNED SEP 20
Long-term memory for AI agents: bitemporal fact ledger, contradiction detection, explainability.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.GetHaki/haki MCP server?
io.github.GetHaki/haki is a hosted endpoint at https://api.gethaki.space/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.gethaki.space
claude mcp add --transport http gethaki-haki 'https://api.gethaki.space/mcp/'
{
"mcpServers": {
"gethaki-haki": {
"url": "https://api.gethaki.space/mcp/"
}
}
} {
"servers": {
"gethaki-haki": {
"type": "http",
"url": "https://api.gethaki.space/mcp/"
}
}
} [mcp_servers.gethaki-haki] url = "https://api.gethaki.space/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gethaki-haki": {
"type": "remote",
"url": "https://api.gethaki.space/mcp/",
"enabled": true
}
}
} openclaw mcp add gethaki-haki --url 'https://api.gethaki.space/mcp/' --transport streamable-http
mcp_servers:
gethaki-haki:
url: "https://api.gethaki.space/mcp/" {
"McpServers": {
"gethaki-haki": {
"Transport": "http",
"Url": "https://api.gethaki.space/mcp/"
}
}
} assistant mcp add gethaki-haki -t streamable-http -u 'https://api.gethaki.space/mcp/'
{
"mcpServers": {
"gethaki-haki": {
"type": "http",
"url": "https://api.gethaki.space/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Sept 26 −28
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.gethaki.space/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.gethaki.space | CN=YR2,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | RSA 4096 | SHA256-RSA | 5a1c628412799bfe7ee1effc64a8a98abb8 |
| SANs: api.gethaki.space | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.gethaki.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| gethaki.space. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.gethaki.space/mcp/ | Auth required | 401 | |
| http (plaintext) | http://api.gethaki.space/mcp/ | HTTPS enforced | 302 | https://api.gethaki.space/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
haki_capture ~115
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 dev (HAKI_MCP_AUTOCONSOLIDATE), so the fact is recallable immediately. Content larger than MAX_JSON_BYTES (256 KiB, same bound as POST /v1/capture) is rejected with a typed error.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| kind | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
haki_context ~190
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 (inspectable via haki_inspect), and an explicit `status` ("ok"/"degraded"/"failed") — never treat a degraded or failed response as "no known facts". If the block does not hold what was needed, call this tool again with the SAME query and `exclude_ids` set to the ids already received — it serves the next page of the same ranked list. Do NOT rewrite the query with what was just read: measured on this project's bench, that finds the missing turn less often than asking unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_tokens | integer | – | – |
| exclude_ids | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
haki_correct ~184
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' logs feedback on a recall without changing the fact. Exactly one target required: fact_id (one precise fact, usually seen via haki_context/haki_inspect) OR trace_id (one whole haki_context call). Same mechanism as POST /v1/feedback (app.ledger.submit_feedback): identical effect whatever the call path. Scope resolved by API key (see _resolve_scope) or, self-hosted without a key, by HAKI_MCP_PROJECT_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| fact_id | – | – | – |
| rating | string | yes | – |
| trace_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
haki_forget ~78
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 receipt (forget_id) and the counters of what was done.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
haki_inspect ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.GetHaki/haki MCP server?
io.github.GetHaki/haki is an MCP server listed in the public MCP registry as io.github.GetHaki/haki. Long-term memory for AI agents: bitemporal fact ledger, contradiction detection, explainability. This page covers its hosted endpoint (https://api.gethaki.space/mcp/).
Is the io.github.GetHaki/haki MCP server safe to use?
io.github.GetHaki/haki scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.GetHaki/haki MCP server expose?
io.github.GetHaki/haki exposes 5 tools: haki_context, haki_capture, haki_inspect, haki_forget, haki_correct. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the io.github.GetHaki/haki MCP server require authentication?
Yes. io.github.GetHaki/haki asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.GetHaki/haki MCP server still maintained?
io.github.GetHaki/haki is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.