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/asgard-ai-platform/mcp-shoplineWrote 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/asgard-ai-platform/mcp-shopline/shopline)<a href="https://agentmods.dev/mcp/asgard-ai-platform/mcp-shopline/shopline"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-shopline/shopline/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/asgard-ai-platform/mcp-shopline/shopline"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-shopline/shopline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
shopline 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 11d 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
{
"shopline": {
"command": "python",
"args": [
"mcp_server.py"
],
"cwd": "${PWD}",
"env": {
"PYTHONPATH": "${PWD}",
"SHOPLINE_API_TOKEN": "${SHOPLINE_API_TOKEN}"
}
}
}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.
- 11d ago First seen · 13 lines scan A 1b9f45555b58
shopline is an MCP server published in the GitHub repository asgard-ai-platform/mcp-shopline (20 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-30.
Other mcp servers, from other repositories
inventory-management-ai-mcp
MCP server for inventory management ai. Features reorder point, demand forecast, sku optimizer. From MEOK AI Labs. Runs locally from the inventory-management-ai-mcp Python package.
ecommerce-ai-mcp
AI-powered ecommerce ai MCP server for agents. Supports write product description, optimize pricing, summarize reviews. By MEOK AI Labs. Runs locally from the ecommerce-ai-mcp Python package.
planthire-ai-mcp
AI-powered planthire ai MCP server for agents. Supports search equipment, get rental quote, check availability. By MEOK AI Labs. Runs locally from the planthire-ai-mcp Python package.
price-tracker-ai-mcp
Price Tracker Ai MCP server. Tools: track price, get price history, set alert. Built by MEOK AI Labs. Runs locally from the price-tracker-ai-mcp Python package.
nutrient-document-engine-mcp-server
MCP server for self-hosted Nutrient Document Engine: extract, edit, redact, and annotate documents. Runs locally from the @nutrient-sdk/document-engine-mcp-server npm package. Needs 5 environment variables to run.
chestnyznak-mcp
A local connector for the Chestniy ZNAK API, a Russian system used to verify product marking codes. It runs through the Chestniy ZNAK MCP server and requires an API key environment variable.