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/raelango/medikode-mcp-serverWrote 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/raelango/medikode-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/raelango/medikode-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/raelango/medikode-mcp-server/mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server 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
{ "mcp-server": { "command": "npx", "args": [ "-y", "@medikode/mcp-server" ] } }
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 · 9 lines scan A 5a3e0d10bb1f
mcp-server is an MCP server published in the GitHub repository raelango/medikode-mcp-server (2 stars, last pushed 10mo ago), licensed ISC. 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
fhirhydrant
FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes. Runs locally from the fhirhydrant npm package. Needs 8 environment variables to run.
phi-guard-mcp
MCP server and CLI for detecting, redacting, and auditing PHI before medical text is sent to AI agents. Runs locally from the phi-guard-mcp Python package.
mcp-pii-guard-au
MCP server for Australian PII detection and sanitisation — TFN, Medicare, ABN, ACN, BSB, bank account, drivers licence, passport, Centrelink CRN, and address recognisers with checksum validation, compliance audit logging, built on Presidio. Runs locally from the mcp-pii-guard-au Python package.
phi-guard-mcp
MCP server and CLI for detecting, redacting, and auditing PHI before medical text is sent to AI agents. Runs locally from the phi-guard-mcp Python package.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.