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/scope-bid/scope-mcp/scope-aec-mcp-aecgit clone --depth 1 https://github.com/scope-bid/scope-mcpWrote 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/scope-bid/scope-mcp/scope-aec-mcp-aec)<a href="https://agentmods.dev/mcp/scope-bid/scope-mcp/scope-aec-mcp-aec"><img src="https://agentmods.dev/badge/mcp/scope-bid/scope-mcp/scope-aec-mcp-aec.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aec 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- scope-aec-mcp — 86% identical, 2 lines differ
What it actually says
{
"aec": {
"command": "npx",
"args": [
"-y",
"@scope-bid/scope-aec-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 10 lines scan A d3477e65c72d
aec is an MCP server published in the GitHub repository scope-bid/scope-mcp (1 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
secondhand-mcp
Search Facebook Marketplace, eBay, Depop, and Poshmark from AI — filters, photos, full listings. Runs locally from the secondhand-mcp npm package. Needs 3 environment variables to run.
mcp-cn-commerce
Chinese e-commerce platform MCP servers — let AI agents read merchant business data (Ocean Engine, Douyin Shop, JD.com, Taobao, Pinduoduo). Runs locally from the mcp-cn-commerce Python package. Needs 10 environment variables to run.
tray
MCP server "tray" as configured in tray-tecnologia/tray-api-ai-plugin. Runs locally from the tray-mcp npm package. Needs 1 environment variable to run.
fedlex
MCP server "fedlex" as configured in malkreide/fedlex-mcp. Runs fedlex_mcp.server with python.
fedlex-mcp
MCP Server for Swiss federal law via the Fedlex SPARQL endpoint. Runs locally from the fedlex-mcp Python 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.