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/Zhanyl-tech/slurm-mcpWrote 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/zhanyl-tech/slurm-mcp/slurm-readonly-mcp)<a href="https://agentmods.dev/mcp/zhanyl-tech/slurm-mcp/slurm-readonly-mcp"><img src="https://agentmods.dev/badge/mcp/zhanyl-tech/slurm-mcp/slurm-readonly-mcp/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/zhanyl-tech/slurm-mcp/slurm-readonly-mcp"><img src="https://agentmods.dev/badge/mcp/zhanyl-tech/slurm-mcp/slurm-readonly-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
slurm-readonly-mcp 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 18d 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
{ "slurm-readonly-mcp": { "command": "uvx", "args": [ "slurm-readonly-mcp" ] } }
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.
- 18d ago First seen · 8 lines scan A 69a0cb877430
slurm-readonly-mcp is an MCP server published in the GitHub repository Zhanyl-tech/slurm-mcp (0 stars, last pushed 8d 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-09-28.
Other mcp servers, from other repositories
clio-paraview
MCP server "clio-paraview" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server paraview.
autovault
AutoVault local capability library and MCP compatibility server. Runs locally from the @autoworks-ai/autovault npm package.
engram
Persistent storage for local modules. Runs locally from the engram npm package.
awrelay
A portable client for AitherRelay-shaped agent messaging — findings, alerts and coordination between agents, over real chat channels a human can also read. Runs locally from the awrelay Python package.
almanac
Deterministic, verifiable ephemeris + geomagnetic computation — the numbers language models hallucinate, computed correctly and checked against NOAA and JPL. Runs locally from the almanac-compute Python package.
project-bourne
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. Runs locally from the @project-bourne/mcp npm package.