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/binary16labs/prime-siloInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/binary16labs/prime-silo/memoray)<a href="https://agentmods.dev/mcp/binary16labs/prime-silo/memoray"><img src="https://agentmods.dev/badge/mcp/binary16labs/prime-silo/memoray/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/binary16labs/prime-silo/memoray"><img src="https://agentmods.dev/badge/mcp/binary16labs/prime-silo/memoray.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memoray 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
{
"memoray": {
"command": "node",
"args": [
"memoray/mcp-server/index.js"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 8 lines scan A fe9fcfc24744
memoray is an MCP server published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed today), 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
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
mcp
Model Context Protocol server for Citadel: encrypted memory as MCP tools. Runs locally from the citadeldb-mcp Python package. Needs 1 environment variable to run.
living-memory
An MCP memory server. One memory your agents share — across models, devices and apps. Runs locally from the @nature-labs/lme-mcp npm package.
engram
Your local, private memory layer. Index your notes and files, then recall anything with citations and temporal reasoning — 100% on your machine. Runs locally from the @jnmetacode/engram npm package.