Dakera MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Sep 2026.
Agent memory engine — 86 MCP tools, self-hosted, single Rust binary
What the code does
We read the source, 17 h ago · rules 3dff92dd89df
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Update latest tag
if: ${{ inputs.tag_latest == 'true' }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Dakera MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Dakera MCP
same job, measured the same waySelf-hosted stealth browser for AI agents: Firefox engine + Rust MCP runtime
Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.
Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.
Self-hosted MCP server: pi-coding-agent tools (run_prompt, file ops) over streamable HTTP.
Self-hosted web research for MCP agents.
Local MCP server: detects a game's engine and gives agents native binary analysis/patching tools.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Rust MCP server for binary analysis and reverse engineering.
Dakera MCP — questions
Answers built from our own checks of this server.