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-cloud-integrations/sap-commerce-mcp-serverWrote 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-cloud-integrations/sap-commerce-mcp-server/sap_commerce_mcp_server)<a href="https://agentmods.dev/mcp/commerce-cloud-integrations/sap-commerce-mcp-server/sap_commerce_mcp_server"><img src="https://agentmods.dev/badge/mcp/commerce-cloud-integrations/sap-commerce-mcp-server/sap_commerce_mcp_server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sap_commerce_mcp_server 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 7d 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
{ "sap_commerce_mcp_server": { "command": "uvx", "args": [ "sap_commerce_mcp_server" ] } }
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.
- 7d ago First seen · 8 lines scan A 4051408a619b
sap_commerce_mcp_server is an MCP server published in the GitHub repository commerce-cloud-integrations/sap-commerce-mcp-server (0 stars, last pushed 5mo 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-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.
gunbroker
GunBroker MCP Pack — wraps the GunBroker firearms-marketplace API. Remote server at gateway.pipeworx.io.
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.
ecommerce-intel-mcp
Product intel: Amazon, AliExpress, Shopify, TikTok Shop, ads and search interest. Remote server at themineworks--ecommerce-intel-mcp.apify.actor.
profitlee-mcp
MCP server for the Profitlee ecommerce profit calculator (Amazon FBA/FBM + TikTok Shop). Runs locally from the profitlee-mcp npm package. Needs 2 environment variables to run.
shopping-deals-mcp-server
MCP server "shopping-deals-mcp-server" as configured in jongan69/shopping-deals-mcp-server. Runs locally from the shopping-deals-mcp-server Python package.