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/commerce-docs/microsite-commerce-storefrontWrote 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/commerce-docs/microsite-commerce-storefront/dropins)<a href="https://agentmods.dev/mcp/commerce-docs/microsite-commerce-storefront/dropins"><img src="https://agentmods.dev/badge/mcp/commerce-docs/microsite-commerce-storefront/dropins/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/commerce-docs/microsite-commerce-storefront/dropins"><img src="https://agentmods.dev/badge/mcp/commerce-docs/microsite-commerce-storefront/dropins.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dropins 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 yesterday.
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
{
"dropins": {
"type": "stdio",
"command": "npx",
"args": [
"--yes",
"@dropins/ai-tools"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- yesterday Changed · +1 lines b5d7740b771b
- 5d ago First seen · 9 lines scan A 32175a382e3c
dropins is an MCP server published in the GitHub repository commerce-docs/microsite-commerce-storefront (8 stars, last pushed today), licensed Apache-2.0. 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-26.
Other mcp servers, from other repositories
lemonsqueezy-mcp-server
Lemon Squeezy SDK as MCP server. Give your AI assistant access to payment and subscription data. Runs locally from the lemonsqueezy-mcp-server npm package. Needs 1 environment variable to run.
mcp-samsclub-ads
MCP server for Sam's Club Sponsored Ads APIs. Runs locally from the mcp-samsclub-ads Python package.
amzscout-skill-mcp
Amazon research from AMZScout data: analyze products & niches, keywords/PPC, and brand catalogs. Remote server at chatbot.amzscout.net.
gunbroker
GunBroker MCP Pack — wraps the GunBroker firearms-marketplace API. Remote server at gateway.pipeworx.io.
mcp-shopify-admin
MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts. Runs locally from the mcp-shopify-admin npm package. Needs 9 environment variables to run.
agentbank-merchant-mcp
Merchant-side MCP server for agentbank — read your orders + live Curless wallet balance from Claude, authenticated by your Curless API key via env (no OAuth). Runs locally from the @curless/agentbank-merchant-mcp npm package.