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/grahamton/merchGentWrote 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/grahamton/merchgent/merch-connector)<a href="https://agentmods.dev/mcp/grahamton/merchgent/merch-connector"><img src="https://agentmods.dev/badge/mcp/grahamton/merchgent/merch-connector/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/grahamton/merchgent/merch-connector"><img src="https://agentmods.dev/badge/mcp/grahamton/merchgent/merch-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
merch-connector 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 9d 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
{ "merch-connector": { "command": "npx", "args": [ "-y", "merch-connector" ] } }
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.
- 9d ago First seen · 9 lines scan A 3eef326ad463
merch-connector is an MCP server published in the GitHub repository grahamton/merchGent (0 stars, last pushed 4mo 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
bestprice-shopping
MCP server "bestprice-shopping", hosted remotely at mcp.bestprice.gr, as configured in TheBestCo/bestprice-mcp.
mcp-server-woocommerce
101 tools for WooCommerce store management with field filtering and guided prompts. Runs locally from the @amitgurbani/mcp-server-woocommerce npm package.
shopify-store-builder-mcp
MCP server for building Shopify stores via the Admin GraphQL API: themes, pages, and navigation. Runs locally from the shopify-store-builder-mcp npm package. Needs 4 environment variables to run.
universalcartmerchantgate-mcp
Remote MCP for Universal Cart merchant readiness MCP, structured receipts, audit logs, and reviewer. Remote server at universalcartmerchantgate.clauxel.com.
media-mcp
MCP server exposing Google Gemini media generation APIs as tools for AI agents. Runs locally from the media-mcp Python package.
fake-store-mcp
MCP server for Fake Store API - E-commerce data integration for Claude AI. Runs locally from the fake-store-mcp npm package.