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/Rul1an/assayWrote 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/rul1an/assay/assay-mcp-server)<a href="https://agentmods.dev/mcp/rul1an/assay/assay-mcp-server"><img src="https://agentmods.dev/badge/mcp/rul1an/assay/assay-mcp-server/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/rul1an/assay/assay-mcp-server"><img src="https://agentmods.dev/badge/mcp/rul1an/assay/assay-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
assay-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 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
{ "assay-mcp-server": { "command": "https://github.com/Rul1an/assay/releases/download/v5.5.1/assay-mcp-server-v5.5.1-linux.mcpb", "args": [], "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.
- 9d ago First seen · 7 lines scan A f663ab59511a
assay-mcp-server is an MCP server published in the GitHub repository Rul1an/assay (10 stars, last pushed today), 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
cargo
Structured Rust cargo operations (build, test, clippy) as typed JSON. Runs locally from the @paretools/cargo npm package.
pare-cargo
Pare Cargo ג€” Structured Rust cargo operations (build, test, clippy, fmt, doc) as typed JSON. Runs locally from the @paretools/cargo npm package.
pond
MCP server "pond" as configured in tenequm/pond. Launched with pond-db.
rustunnel
MCP server "rustunnel", hosted remotely at eu.edge.rustunnel.com, as configured in joaoh82/rustunnel. Needs 1 environment variable to run.
cc-audit
MCP server "cc-audit" as configured in ryo-ebata/cc-audit. Launched with ./target/release/cc-audit serve.
octobrain
MCP server "octobrain" as configured in Muvon/octobrain. Launched with https://github.com/Muvon/octobrain/releases/download/0.9.4/octobrain-0.9.4-aarch.