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/berekvolgyipeter/dotclaudeInstalling this writes the configuration, not the program: `sh` has to be on your PATH already, or the server will not start.
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/berekvolgyipeter/dotclaude/claude-context)<a href="https://agentmods.dev/mcp/berekvolgyipeter/dotclaude/claude-context"><img src="https://agentmods.dev/badge/mcp/berekvolgyipeter/dotclaude/claude-context/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/berekvolgyipeter/dotclaude/claude-context"><img src="https://agentmods.dev/badge/mcp/berekvolgyipeter/dotclaude/claude-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-context 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
{
"claude-context": {
"type": "stdio",
"command": "sh",
"args": [
"-c",
"export $(grep '^OPENAI_API_KEY=' .env | xargs) && exec npx --yes @zilliz/claude-context-mcp@latest"
],
"env": {
"OPENAI_API_KEY": "${OPENAI_API_KEY}",
"MILVUS_ADDRESS": "localhost:19531"
}
}
}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 · 14 lines scan A 69660c76ed3f
claude-context is an MCP server published in the GitHub repository berekvolgyipeter/dotclaude (2 stars, last pushed 6d 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-31.
Other mcp servers, from other repositories
rag-knowledge-graph-mcp
Rag Knowledge Graph automation via MCP. Includes index document, rag query, add graph edge. By MEOK AI Labs. Runs locally from the rag-knowledge-graph-mcp Python package.
ragie
Ingest, manage, and retrieve documents for RAG-powered AI applications. Runs locally from the mcparmory-ragie Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.