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/fieldcure/fieldcure-mcp-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/fieldcure/fieldcure-mcp-rag/mcp-rag)<a href="https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-rag/mcp-rag"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-rag/mcp-rag/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/fieldcure/fieldcure-mcp-rag/mcp-rag"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-rag/mcp-rag.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rag 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 9d 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
{
"rag": {
"command": "FieldCure.Mcp.Rag",
"args": [],
"env": {
"OPENAI_API_KEY": "{openai_api_key}",
"ANTHROPIC_API_KEY": "{anthropic_api_key}",
"GEMINI_API_KEY": "{gemini_api_key}",
"VOYAGE_API_KEY": "{voyage_api_key}",
"GROQ_API_KEY": "{groq_api_key}"
}
}
}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.
- 9d ago First seen · 13 lines scan A 8b443f3ec38c
rag is an MCP server published in the GitHub repository fieldcure/fieldcure-mcp-rag (0 stars, last pushed 3mo 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
inspeximus
MCP server "inspeximus" as configured in DanceNitra/inspeximus. Runs locally from the inspeximus[mcp] Python package. Needs 1 environment variable to run.
kioku
MCP server "kioku" as configured in sandovaldavid/kioku. Launched with kioku. Needs 3 environment variables to run.
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.
rag-knowledge-mcp
MCP server for rag knowledge. Features semantic search, knowledge graph query, index document. From MEOK AI Labs. Runs locally from the rag-knowledge-mcp Python package.
governed-rag-mcp
MCP server "governed-rag-mcp" as configured in Rlealbarili/governed-rag-mcp. Runs locally from the governed-rag-mcp Python package.
inkdex
MCP server that indexes markdown docs and exposes hybrid semantic search for LLM context retrieval. Runs locally from the inkdex npm package.