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/Byron2306/EdgeK-BEASTWrote 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/byron2306/edgek-beast/memory)<a href="https://agentmods.dev/mcp/byron2306/edgek-beast/memory"><img src="https://agentmods.dev/badge/mcp/byron2306/edgek-beast/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/byron2306/edgek-beast/memory"><img src="https://agentmods.dev/badge/mcp/byron2306/edgek-beast/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 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
{
"memory": {
"args": [
"-y",
"@modelcontextprotocol/server-memory"
],
"command": "npx"
}
}What else mcp.json configures
This page is one entry in a file that holds 10. Installing the file brings all of them; each is measured and scanned on its own page.
- MCP server edgek-beast A not measured
- MCP server fetch A not measured
- MCP server filesystem A not measured
- MCP server git A not measured
- MCP server github A not measured
- MCP server playwright A not measured
- MCP server postgres A not measured
- MCP server sequential-thinking A not measured
- MCP server sqlite A not measured
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 5072d32794ea
memory is an MCP server published in the GitHub repository Byron2306/EdgeK-BEAST (5 stars, last pushed 5d 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-09-18.
Other mcp servers, from other repositories
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.
amnesic
The MCP server with the most ironic name in the registry — persistent semantic memory for your SQL databases. Runs locally from the amnesic Python package.
rememb
Persistent memory standard for AI agents — local, portable, zero config. Runs locally from the rememb Python package.
memory
Persistent memory for AI assistants. Store, search, and recall across sessions. Runs locally from the velixar-mcp-server npm package. Needs 1 environment variable to run.
memgit
MCP server "memgit" as configured in code4161/memgit. Launched with memgit serve.
project-memory-mcp
Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo. Runs locally from the @kaaustubh/project-memory-mcp npm package. Needs 1 environment variable to run.