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/Ricardo-Kaminski/local-ragWrote 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/ricardo-kaminski/local-rag/lightrag)<a href="https://agentmods.dev/mcp/ricardo-kaminski/local-rag/lightrag"><img src="https://agentmods.dev/badge/mcp/ricardo-kaminski/local-rag/lightrag/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/ricardo-kaminski/local-rag/lightrag"><img src="https://agentmods.dev/badge/mcp/ricardo-kaminski/local-rag/lightrag.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lightrag 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 10d 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
{
"lightrag": {
"command": "C:\\Users\\ricar\\miniconda3\\envs\\local-rag\\python.exe",
"args": [
"C:\\workspace\\pessoal\\local-rag\\mcp_server.py"
],
"cwd": "C:\\workspace\\pessoal\\local-rag"
}
}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.
- 10d ago First seen · 9 lines scan A 0d47370de0cb
lightrag is an MCP server published in the GitHub repository Ricardo-Kaminski/local-rag (2 stars, last pushed 5mo 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
myrmion-graphrag
MCP server "myrmion-graphrag" as configured in e2its/myrmion-graphrag. Runs locally from the myrmion-graphrag Python package.
lightrag_mcp
MCP Server for LightRAG. Runs locally from the lightrag_mcp Python package.
lightrag-mcp
MCP server for LightRag. Runs locally from the lightrag-mcp npm package.
edgequake-metals
MCP server "edgequake-metals", hosted remotely at localhost, as configured in raphaelmansuy/edgequake.
trip2g
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers. Remote server at trip2g.com.
r2r
MCP server "r2r" as configured in mm-weber/loremaester. Runs /workspaces/loremaester/mcp-servers/r2r-wrapper/r2r_mcp_wrapper.py with python3. Needs 1 environment variable to run.