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/edithatogo/mchsWrote 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/edithatogo/mchs/registry-mchs)<a href="https://agentmods.dev/mcp/edithatogo/mchs/registry-mchs"><img src="https://agentmods.dev/badge/mcp/edithatogo/mchs/registry-mchs/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/edithatogo/mchs/registry-mchs"><img src="https://agentmods.dev/badge/mcp/edithatogo/mchs/registry-mchs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mchs 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 8d 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
{
"mchs": {
"command": "uvx",
"args": [
"nwau-py"
],
"env": {}
}
}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.
- 8d ago First seen · 9 lines scan A e1d4f09c3f23
mchs is an MCP server published in the GitHub repository edithatogo/mchs (3 stars, last pushed 7d 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
chemistry
The fast, Pythonic way to build MCP servers and clients. Runs locally from the fastmcp Python package.
medical-terminologies-mcp
Diagnoses, drugs & lab codes: ICD-11, SNOMED, LOINC, RxNorm, MeSH, ATC, CID-10. 37 tools, MIT. Runs locally from the medical-terminologies-mcp npm package. Needs 7 environment variables to run.
icf-mcp
WHO ICF codes: lookup, search, hierarchy, qualifiers, and 11 scored clinical assessment instruments. Remote server at mcp-icf.medseal.app.
icdwise
Verified ICD-10-CM code lookup & validation for AI agents — official descriptions, not guesses. Runs locally from the icdwise npm package.
clinicaltrials-mcp
Conversational access to ClinicalTrials.gov — an MCP server for pharma analysts, CRO teams, and health-tech builders. Runs locally from the clinicaltrials-mcp Python package.
medterms-mcp
Medical terminology MCP server — ICD-10, MedDRA, RxNorm, CTCAE for AI agents. Runs locally from the medterms-mcp npm package.