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/PO-VINCENT/ai-shopping-auditWrote 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/po-vincent/ai-shopping-audit/catalogready)<a href="https://agentmods.dev/mcp/po-vincent/ai-shopping-audit/catalogready"><img src="https://agentmods.dev/badge/mcp/po-vincent/ai-shopping-audit/catalogready/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/po-vincent/ai-shopping-audit/catalogready"><img src="https://agentmods.dev/badge/mcp/po-vincent/ai-shopping-audit/catalogready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
catalogready 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 12d 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
{
"catalogready": {
"command": "uv",
"args": [
"run",
"catalogready-mcp"
],
"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.
- 12d ago First seen · 10 lines scan A 492ee8f7ff12
catalogready is an MCP server published in the GitHub repository PO-VINCENT/ai-shopping-audit (5 stars, last pushed 1mo ago), 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-08-31.
Other mcp servers, from other repositories
shopify-geo-audit
Audit any Shopify store for AI search (GEO/AEO) readiness and generate the fixes. No signup. Runs locally from the shopify-geo-audit-mcp npm package.
gengeo
Merchant verification for AI shopping agents. Remote server at mcp.gengeo.co.
agentmart
First AI Agent e-commerce marketplace with 74+ AI products, MCP protocol, and Alipay payments. Remote server at api.ai-gaoqian.xyz.
livostyle-catalog-mcp
MCP server giving AI agents (Claude Desktop, Cursor, Cline, Cowork) live access to Livostyle.com — a 2,766-SKU US women's fashion catalog with reviews, variants, taxonomy, and pricing. Drop-in shopping context for any agent. Runs locally from the livostyle-catalog-mcp npm package.
agent-signal
Collective intelligence for AI shopping agents — product intel, deals, and more. Runs locally from the agent-signal npm package.
optifeed-radar
AI visibility checker: does AI recommend your brand? GEO/AEO, runs locally, BYO keys. CLI + MCP. Runs locally from the optifeed-radar npm package. Needs 4 environment variables to run.