io.github.Dakera-AI/dakera-mcp
OCI · GHCR.IO/DAKERA-AI/DAKERA-MCP:0.10.12 · SCANNED SEP 20
Agent memory engine — 86 MCP tools, self-hosted, single Rust binary
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1581 tokens (~112/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.Dakera-AI/dakera-mcp server?
io.github.Dakera-AI/dakera-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/dakera-ai/dakera-mcp:0.10.12. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/dakera-ai/dakera-mcp:0.10.12
claude mcp add dakera-ai-dakera-mcp -- docker run --rm -i ghcr.io/dakera-ai/dakera-mcp:0.10.12
{
"mcpServers": {
"dakera-ai-dakera-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/dakera-ai/dakera-mcp:0.10.12"
]
}
}
} {
"servers": {
"dakera-ai-dakera-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/dakera-ai/dakera-mcp:0.10.12"
]
}
}
} codex mcp add dakera-ai-dakera-mcp -- docker run --rm -i ghcr.io/dakera-ai/dakera-mcp:0.10.12
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dakera-ai-dakera-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/dakera-ai/dakera-mcp:0.10.12"
],
"enabled": true
}
}
} mcp_servers:
dakera-ai-dakera-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/dakera-ai/dakera-mcp:0.10.12"] {
"McpServers": {
"dakera-ai-dakera-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/dakera-ai/dakera-mcp:0.10.12"
]
}
}
} {
"mcpServers": {
"dakera-ai-dakera-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/dakera-ai/dakera-mcp:0.10.12"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 3 Sept 26 35
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 · Analysed oci/ghcr.io/dakera-ai/dakera-mcp:0.10.12
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
dakera_batch_forget ~145
Bulk-delete memories matching filter criteria: tags, importance range, time window, or memory type. At least one filter is required to prevent accidental full-agent wipe. Deletion is permanent — use dakera_memory_importance to lower importance scores instead of deleting.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| created_after | integer | – | After Unix timestamp |
| created_before | integer | – | Before Unix timestamp |
| max_importance | number | – | Max importance threshold |
| memory_type | string | – | – |
| min_importance | number | – | Min importance threshold |
| session_id | string | – | – |
| tags | array | – | Tags to match (all required) |
No output schema declared.
No examples provided.
dakera_batch_recall ~133
Filter-based memory listing by tags, importance range, time window, type, or session. Prefer over dakera_recall when semantic search is not needed. At least one filter required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| created_after | integer | – | After Unix timestamp |
| created_before | integer | – | Before Unix timestamp |
| max_importance | number | – | Max importance (inclusive) |
| memory_type | string | – | – |
| min_importance | number | – | Min importance (inclusive) |
| session_id | string | – | – |
| tags | array | – | Tags to match (all required) |
No output schema declared.
No examples provided.
dakera_discover_tools ~90
Search the Dakera tool catalog by keyword or tier (core/power/admin/meta) and return names and one-line summaries without loading full schemas. Call this first to find relevant tools, then use dakera_load_tools to fetch only the schemas you need — avoids loading the full catalog upfront.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Keyword to search tool names/descriptions. |
| tier | string | – | – |
No output schema declared.
No examples provided.
dakera_extract ~181
Extract structured information (entities, topics, key phrases, summary) from arbitrary text using the configured provider hierarchy: per-request override → namespace default → server default → GLiNER local. Supported providers: `gliner` (zero-config local ONNX), `openai`, `anthropic`, `openrouter`, `ollama`, `none`.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_types | array | – | GLiNER entity type labels (e.g. ["person", "org", "location"]). Only used when provider is `gliner`. |
| extractor_override | object | – | Per-request provider override — highest priority in the resolution hierarchy. Fields: provider, model, base_url, api_key. |
| namespace | string | – | Namespace whose default extractor config is used. If omitted, the server-level default is used. |
| text | string | yes | Text to extract information from |
No output schema declared.
No examples provided.
dakera_forget ~87
Permanently delete memories by ID or tag. Provide memory_ids for exact removal or tags to bulk-delete all memories sharing those tags. Deletion is immediate and irreversible — prefer dakera_memory_importance to suppress without deleting.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| memory_ids | array | – | Specific memory IDs to delete |
| tags | array | – | Delete memories with these tags |
No output schema declared.
No examples provided.
dakera_fulltext_search ~92
BM25 keyword search over indexed documents. Use over vector search when exact-term recall matters (error codes, IDs, names). For semantic+keyword combined use dakera_hybrid_search.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional metadata filter |
| namespace | string | yes | Namespace to search in |
| query | string | yes | Search query text |
| top_k | integer | – | Number of results to return |
No output schema declared.
No examples provided.
dakera_hybrid_search ~175
BM25 + vector ANN hybrid search in a single pass. Omit vector for BM25-only mode. Use for RAG when pure semantic or keyword search alone is insufficient. vector_weight: 0.0=BM25, 1.0=vector (default 0.5).
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional metadata filter |
| include_metadata | boolean | – | – |
| include_vectors | boolean | – | – |
| namespace | string | yes | Namespace to search in |
| text | string | yes | Text query for full-text search |
| top_k | integer | – | Number of results to return |
| vector | array | – | Query embedding; omit for BM25-only. |
| vector_weight | number | – | Vector score weight 0.0–1.0; text weight = 1−value. |
No output schema declared.
No examples provided.
dakera_knowledge_graph ~105
Build a knowledge graph from a seed memory using embedding similarity. Use to explore how a concept connects to stored knowledge. For BFS traversal of an existing linked graph use dakera_graph_traverse.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| depth | integer | – | Graph traversal depth (controls candidate count) |
| memory_id | string | yes | Seed memory ID to build graph from |
| min_similarity | number | – | Minimum similarity threshold 0.0-1.0 |
No output schema declared.
No examples provided.
dakera_load_tools ~58
Fetch the full inputSchema for one or more named tools. Use after dakera_discover_tools. Returns schemas for found tools and a not_found list for unrecognized names.
| Name | Type | Req | Description |
|---|---|---|---|
| tools | array | yes | Tool names to load schemas for |
No output schema declared.
No examples provided.
dakera_recall ~145
Retrieve top-k memories semantically closest to a query. Prefer over dakera_batch_recall for query-based retrieval. Set include_associated=true to expand results via KG edges (1-3 hops).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| include_associated | boolean | – | Include KG-linked memories in results |
| min_importance | number | – | Min importance threshold |
| query | string | yes | Semantic query text |
| since | string | – | Only memories created at or after this ISO-8601 timestamp |
| top_k | integer | – | Max results to return |
| until | string | – | Only memories created at or before this ISO-8601 timestamp |
No output schema declared.
No examples provided.
dakera_search ~92
Semantic search with optional tag and memory-type pre-filters. Prefer over dakera_recall when results must be constrained by tag or type alongside the semantic match.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| memory_type | string | – | Filter by memory type |
| query | string | yes | Search query text |
| tags | array | – | Filter by tags |
| top_k | integer | – | Number of results |
No output schema declared.
No examples provided.
dakera_session_end ~67
Close an active session with an optional summary. Always call at run end (even on error) to avoid orphaned sessions; summary is retrievable via dakera_session_get.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session ID to end |
| summary | string | – | Optional session summary |
No output schema declared.
No examples provided.
dakera_session_start ~59
Open a new session, returning a session_id that groups stored memories under a shared context. Attach metadata such as task type or trigger source for later retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| metadata | object | – | Optional session metadata |
No output schema declared.
No examples provided.
dakera_store ~152
Persist a new memory for an agent with importance weighting and optional tags. Use to save facts, decisions, or context for future retrieval. importance defaults to 0.5; set 0.8–1.0 for critical memories that must survive decay.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| content | string | yes | Memory content text |
| expires_at | integer | – | Expiry Unix timestamp (seconds) |
| importance | number | – | Importance 0.0-1.0 |
| memory_type | string | – | Memory type (episodic|semantic|procedural|working) |
| session_id | string | – | Session to associate with |
| tags | array | – | Tags for filtering |
No output schema declared.
No examples provided.
What is the io.github.Dakera-AI/dakera-mcp server?
io.github.Dakera-AI/dakera-mcp is listed in the public MCP registry as io.github.Dakera-AI/dakera-mcp. Agent memory engine, 86 MCP tools, self-hosted, single Rust binary. This page covers its container image (ghcr.io/dakera-ai/dakera-mcp:0.10.12).
Is the io.github.Dakera-AI/dakera-mcp server safe to use?
io.github.Dakera-AI/dakera-mcp scores 43 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.Dakera-AI/dakera-mcp server expose?
io.github.Dakera-AI/dakera-mcp exposes 14 tools: dakera_store, dakera_recall, dakera_forget, dakera_batch_recall, dakera_batch_forget, and 9 more. Their descriptions and schemas cost roughly 1,581 tokens of context every time the server is loaded.
Is the io.github.Dakera-AI/dakera-mcp server still maintained?
io.github.Dakera-AI/dakera-mcp 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.