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/giskard09/giskard-memoryWrote 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/giskard09/giskard-memory/memory)<a href="https://agentmods.dev/mcp/giskard09/giskard-memory/memory"><img src="https://agentmods.dev/badge/mcp/giskard09/giskard-memory/memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/giskard09/giskard-memory/memory"><img src="https://agentmods.dev/badge/mcp/giskard09/giskard-memory/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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 1mo 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
{ "memory": { "url": "https://memory.rgiskard.xyz/sse", "type": "sse" } }
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.
- 1mo ago First seen · 6 lines scan A f9e39a4fd1a6
memory is an MCP server published in the GitHub repository giskard09/giskard-memory (0 stars, last pushed 12d ago), licensed Apache-2.0. 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
xaip-mcp-server
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL. Runs locally from the xaip-mcp-server npm package.
webbersites-x402-mcp
45 pay-per-call AI agent tools + wallet-owned agent memory. Scraping, SEO, lint, crypto. x402 USDC. Runs locally from the webbersites-x402-mcp npm package. Needs 2 environment variables to run.
chainmemory
Persistent cross-model memory for AI agents: verifiable, portable, client-side encrypted. Runs locally from the chainmemory-mcp npm package. Needs 5 environment variables to run.
soroban-memory
Persistent memory layer for Stellar/Soroban projects. Scans your repo, links code to on-chain reality, and serves the result to you and to your AI agents over MCP. Runs locally from the soroban-memory npm package.
mcp
TPermanent memory layer for AI agents. Mint moments to the Polygon blockchain via MCP. Remote server at mcp.hekkova.com.
fidelis-memory
Fidelis Memory: faithful agent memory with zero-LLM retrieval by default. By Hermes Labs. Runs locally from the fidelis-memory Python package. Needs 1 environment variable to run.