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/ShoppingResult/shoppingscraper-cliWrote 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/shoppingresult/shoppingscraper-cli/cli)<a href="https://agentmods.dev/mcp/shoppingresult/shoppingscraper-cli/cli"><img src="https://agentmods.dev/badge/mcp/shoppingresult/shoppingscraper-cli/cli/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/shoppingresult/shoppingscraper-cli/cli"><img src="https://agentmods.dev/badge/mcp/shoppingresult/shoppingscraper-cli/cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cli 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
{ "cli": { "command": "npx", "args": [ "-y", "@shoppingscraper/cli" ] } }
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 · 9 lines scan A 482af3b8ce48
cli is an MCP server published in the GitHub repository ShoppingResult/shoppingscraper-cli (2 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
goofish
A local command-line connection to 闲鱼, a Chinese online marketplace, exposed for use by an AI agent.
thunderbird-cli
Give AI agents full read/write email access via Mozilla Thunderbird. Zero credentials. Runs locally from the thunderbird-cli-mcp npm package. Needs 2 environment variables to run.
sipcode
Sip your tokens, don't gulp them. Keep Claude Code's context clean: drift detection, re-read dedup, integrity scoring, AST-aware reads, and 15 MCP tools for Claude Desktop. Runs locally from the sipcode npm package.
avito-mcp
MCP server for Avito: chats, listings, orders and analytics, with previews and confirmations. Runs locally from the avito-mcp npm package. Needs 4 environment variables to run.
lemonsqueezy-mcp
LemonSqueezy MCP server for managing your store from AI assistants. Runs locally from the @yawlabs/lemonsqueezy-mcp npm package.
labellevie-mcp
MCP server "labellevie-mcp" as configured in McCANNParis/MCPServerLaBelleVie. Runs locally from the labellevie-mcp npm package.