Borrowing it
Nothing to install: this file belongs to danielsimonjr/memory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/danielsimonjr/memory-mcp/main/.claude/settings.jsongit clone --depth 1 https://github.com/danielsimonjr/memory-mcpWrote 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/settings/danielsimonjr/memory-mcp/settings)<a href="https://agentmods.dev/settings/danielsimonjr/memory-mcp/settings"><img src="https://agentmods.dev/badge/settings/danielsimonjr/memory-mcp/settings/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/settings/danielsimonjr/memory-mcp/settings"><img src="https://agentmods.dev/badge/settings/danielsimonjr/memory-mcp/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory-mcp 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"project": {
"name": "MCP Servers Collection",
"description": "Collection of 14 specialized Model Context Protocol servers (10 local + 4 global packages)",
"type": "multi-server-repository"
},
"defaultServer": "memory-mcp",
"enabledServers": [
"deepthinking-mcp",
"markitdown-mcp",
"math-mcp",
"memory-mcp",
"fzf-mcp",
"sequential-thinking-mcp",
"playwright",
"time",
"windows-mcp"
],
"disabledServers": [
"everything-mcp",
"substack-mcp"
],
"platformSpecific": {
"windows": {
"required": ["everything-mcp"],
"optional": []
},
"crossPlatform": [
"deepthinking-mcp",
"fzf-mcp",
"markitdown-mcp",
"math-mcp",
"memory-mcp",
"fermat-mcp",
"remember-mcp",
"substack-mcp"
]
},
"serverCategories": {
"reasoning": ["deepthinking-mcp", "sequential-thinking-mcp"],
"mathematics": ["math-mcp", "fermat-mcp"],
"memory": ["memory-mcp", "remember-mcp"],
"search": ["everything-mcp", "fzf-mcp"],
"conversion": ["markitdown-mcp"],
"integration": ["substack-mcp"],
"automation": ["playwright", "windows-mcp"],
"utilities": ["time"]
},
"buildRequirements": {
"typescript": {
"servers": ["deepthinking-mcp", "math-mcp", "memory-mcp", "substack-mcp"],
"buildCommand": "npm run build",
"entryPoint": "dist/"
},
"javascript": {
"servers": ["everything-mcp", "fzf-mcp"],
"buildCommand": null,
"entryPoint": "index.js"
},
"python": {
"servers": ["fermat-mcp", "markitdown-mcp", "remember-mcp", "time"],
"buildCommand": null,
"entryPoint": "server.py",
"pythonVersion": "3.10+"
},
"globalPackages": {
"servers": ["sequential-thinking-mcp", "playwright", "windows-mcp"],
"note": "Installed globally via npm install -g <package>"
}
},
"dependencies": {
"external": {
"everything-mcp": {
"name": "Everything",
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.
- 2mo ago First seen · 154 lines scan A a79b8d9a1b5d
memory-mcp is a settings file published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
memory-mcp compared with settings from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| memory-mcpdanielsimonjr/memory-mcp | Settings file | 3 | 4d ago | MIT | A | — | Claude Code |
| supabasesupabase/supabase | Settings file | 115k | yesterday | Apache-2.0 | A | — | Claude Code |
| supersetapache/superset | Settings file | 75k | yesterday | Apache-2.0 | A | — | Claude Code |
| RuViewruvnet/RuView | Settings file | 103k | yesterday | MIT | A | — | Claude Code |
| claude-cookbooksanthropics/claude-cookbooks | Settings file | 54k | 2d ago | MIT | A | — | Claude Code |
| ormprisma/orm | Settings file | 48k | yesterday | Apache-2.0 | A | — | Claude Code |
| claude-code-best-practiceshanraisshan/claude-code-best-practice | Settings file | 69k | yesterday | MIT | A | — | Claude Code |