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/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/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/nixrajput/portfolio-nextjs/memory"><img src="https://agentmods.dev/badge/mcp/nixrajput/portfolio-nextjs/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": {
"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.
- 1mo ago First seen · 10 lines scan A f5cc892415d8
memory is an MCP server published in the GitHub repository nixrajput/portfolio-nextjs (151 stars, last pushed 28d 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
MCP server "todox", hosted remotely at www.todox.dev, as configured in beydemirfurkan/todox.
graft
MCP server "graft" as configured in haikelz/ikuyo. Launched with graft mcp.
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.
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.
chronicle-mcp
Local MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. Runs locally from the chronicle-mcp-server Python package.
server-memory
The agentage Memory MCP server: exposes your local vaults as the frozen 6 memory tools over stdio. The open, cross-vendor counterpart to @modelcontextprotocol/server-memory. Runs locally from the @agentage/server-memory npm package.