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.
npx agentmods add mcp/nixrajput/portfolio-nextjs/memorygit clone --depth 1 https://github.com/nixrajput/portfolio-nextjsWrote 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/nixrajput/portfolio-nextjs/memory)<a href="https://agentmods.dev/mcp/nixrajput/portfolio-nextjs/memory"><img src="https://agentmods.dev/badge/mcp/nixrajput/portfolio-nextjs/memory.svg" alt="Measured on agentmods" 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 4d 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": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. 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.
- 4d ago First seen · 10 lines scan A f5cc892415d8
memory is an MCP server published in the GitHub repository nixrajput/portfolio-nextjs (145 stars, last pushed 17d 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-30.
Other mcp servers, from other repositories
todox
Memory for coding agents: the decisions, the dead ends, and where the last session stopped. Remote server at www.todox.dev.
agenticscope
A directory-as-context standard plus a read-only MCP server that gives AI agents live, structured, token-budgeted awareness of a multi-project workspace. Runs locally from the agenticscope npm package.
ruflo
Ruflo - Enterprise AI agent orchestration platform. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration. Runs locally from the ruflo npm package. Needs 6 environment variables to run.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.