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/auxiliar-ai/auxiliar-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/auxiliar-ai/auxiliar-mcp/auxiliar)<a href="https://agentmods.dev/mcp/auxiliar-ai/auxiliar-mcp/auxiliar"><img src="https://agentmods.dev/badge/mcp/auxiliar-ai/auxiliar-mcp/auxiliar/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/auxiliar-ai/auxiliar-mcp/auxiliar"><img src="https://agentmods.dev/badge/mcp/auxiliar-ai/auxiliar-mcp/auxiliar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
auxiliar 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 11d 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
{
"auxiliar": {
"command": "npx",
"args": [
"auxiliar-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.
- 11d ago First seen · 8 lines scan A 8eca19d7ae39
auxiliar is an MCP server published in the GitHub repository auxiliar-ai/auxiliar-mcp (0 stars, last pushed 2mo 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
crawlforge-mcp-server
Web scraping, crawling, deep research & autonomous extraction — 29 MCP tools, clean Markdown/JSON. Runs locally from the crawlforge-mcp-server npm package. Needs 3 environment variables to run.
mcp
MCP server for the Synoppy web-data API — read, screenshot, crawl, map, search, extract, classify, enrich, and images as tools for any MCP client. Runs locally from the @synoppy/mcp npm package.
hatfetch
Give any LLM agent the power to read any website — even the ones that block bots. An MCP server that returns clean Markdown and handles blocks automatically via residential proxies. Runs locally from the hatfetch npm package.
Scrapling
Scrapling is an undetectable, powerful, flexible, high-performance Python library that makes Web Scraping easy and effortless as it should be! Runs locally from the scrapling Python package.
uisight
AI and human share live mobile+desktop browser sessions; measured UI findings your agent can act on. Runs locally from the uisight npm package. Needs 3 environment variables to run.
crw
MCP server for CRW web scraper — scrape, crawl, map, extract, search, and PDF-parse tools for AI agents. Runs locally from the crw-mcp npm package.