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/intersystems-community/medical-graphrag-assistantWrote 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/intersystems-community/medical-graphrag-assistant/gemini-impl)<a href="https://agentmods.dev/mcp/intersystems-community/medical-graphrag-assistant/gemini-impl"><img src="https://agentmods.dev/badge/mcp/intersystems-community/medical-graphrag-assistant/gemini-impl.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gemini-impl 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 6d 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
{
"gemini-impl": {
"type": "stdio",
"command": "~/ws/productivity-framework/tools/gemini-mcp/venv/bin/python",
"args": [
"~/ws/productivity-framework/tools/gemini-mcp/gemini_mcp_server.py"
],
"env": {
"GEMINI_API_KEY": "${GEMINI_API_KEY}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 6d ago First seen · 12 lines scan A 4070f395036e
gemini-impl is an MCP server published in the GitHub repository intersystems-community/medical-graphrag-assistant (0 stars, last pushed 7mo 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
code-review-graph
Local-first knowledge graph for token-efficient code review through MCP and CLI. Runs locally from the code-review-graph Python package.
mcp
Securely access and manage FHIR healthcare data stored in Medplum. Remote server at api.medplum.com.
octocode
AI-powered code indexer with semantic search and knowledge graphs. Runs locally from the @muvon/octocode npm package.
jurisd
MCP server "jurisd" as configured in russellbrenner/jurisd. Runs dist/index.js with node.
healthclaw-local
MCP server "healthclaw-local", hosted remotely at localhost, as configured in aks129/HealthClawGuardrails.
healthclaw-guardrails
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. Remote server at mcp-server-production-5112.up.railway.app.