Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/the-essential/reliqueryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/the-essential/reliquery/mempalace)<a href="https://agentmods.dev/mcp/the-essential/reliquery/mempalace"><img src="https://agentmods.dev/badge/mcp/the-essential/reliquery/mempalace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mempalace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mempalace": {
"command": "python",
"args": [
"-m",
"mempalace.mcp_server"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 9 lines scan A bf07fb41ee6a
mempalace is an MCP server published in the GitHub repository the-essential/reliquery (5 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
memory
MCP server "memory" as configured in Yupcha/memXT. Launched with ${HOME}/.memxt/bin/memxt mcp. Needs 2 environment variables to run.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
simple-rick
MCP server "simple-rick" as configured in good-v1be/simple-rick. Runs locally from the simple-rick npm package.
sthayi
Local-first AI memory over MCP. No account; you own the store. Runs locally from the sthayi npm package.
thor
MCP server "thor" as configured in nworks3d/THOR-memory-bible-for-AI. Runs in Docker (ghcr.io/nworks3d/thor-mcp:2.1.1).