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.
npx agentmods add mcp/luispintoapify/ecommerce-agent-starter/apify-ecommercegit clone --depth 1 https://github.com/luispintoapify/ecommerce-agent-starterWrote 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/luispintoapify/ecommerce-agent-starter/apify-ecommerce)<a href="https://agentmods.dev/mcp/luispintoapify/ecommerce-agent-starter/apify-ecommerce"><img src="https://agentmods.dev/badge/mcp/luispintoapify/ecommerce-agent-starter/apify-ecommerce.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
apify-ecommerce 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 4d 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
{
"apify-ecommerce": {
"url": "https://mcp.apify.com?tools=apify/e-commerce-scraping-tool"
}
}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.
- 4d ago First seen · 5 lines scan A 8bffead4382e
apify-ecommerce is an MCP server published in the GitHub repository luispintoapify/ecommerce-agent-starter (3 stars, last pushed 7d 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
mcp-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.
forkable-mcp
Unofficial MCP server for Forkable — order and manage corporate lunches from any MCP client. Runs locally from the forkable-mcp npm package.
labellevie-mcp
MCP server "labellevie-mcp" as configured in McCANNParis/MCPServerLaBelleVie. Runs locally from the labellevie-mcp npm package.
shopify-mcp
MCP server for Shopify Admin API — product, order, customer, inventory, and fulfillment management. Runs locally from the @purplesquirrel/shopify-mcp npm package.
shippo-mcp
MCP server "shippo-mcp", hosted remotely at mcp.shippo.com, as configured in goshippo/ai.
shippo-mcp
Multi-carrier shipping for AI agents: compare rates, buy labels, track packages, validate addresses. Remote server at mcp.shippo.com.