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/alexar76/argusWrote 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/alexar76/argus/argus3)<a href="https://agentmods.dev/mcp/alexar76/argus/argus3"><img src="https://agentmods.dev/badge/mcp/alexar76/argus/argus3/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/alexar76/argus/argus3"><img src="https://agentmods.dev/badge/mcp/alexar76/argus/argus3.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
argus3 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 1mo 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
{
"argus3": {
"command": "npx",
"args": [
"-y",
"@alexar76/argus3"
],
"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.
- 1mo ago First seen · 10 lines scan A 7bd7a03cb63d
argus3 is an MCP server published in the GitHub repository alexar76/argus (2 stars, last pushed yesterday), 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
t2000
MCP server "t2000", hosted remotely at mcp.t2000.ai, as configured in mission69b/t2000.
froglet
MCP server for local Froglet verifiable compute, signed receipts, settlement, and service publication. Runs locally from the froglet-mcp npm package. Needs 5 environment variables to run.
aigen
MCP server "aigen", hosted remotely at cryptogenesis.duckdns.org, as configured in Aigen-Protocol/aigen-protocol.
safe-agent
Open bounty protocol for AI agents. 22 tools: token safety scans + paid missions. 0.5% fee. Remote server at cryptogenesis.duckdns.org.
aimarket-plugins
Package products as ready-to-run MCP servers for Claude Desktop. Runs locally from the aimarket-mcp-packager Python package. Needs 1 environment variable to run.
sanctionsai
OFAC sanctions screening for AI agents: screen names, wallets, entities against the SDN list. Remote server at sanctionsai.dev.