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/theYahia/boxberry-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/theyahia/boxberry-mcp/boxberry)<a href="https://agentmods.dev/mcp/theyahia/boxberry-mcp/boxberry"><img src="https://agentmods.dev/badge/mcp/theyahia/boxberry-mcp/boxberry/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/theyahia/boxberry-mcp/boxberry"><img src="https://agentmods.dev/badge/mcp/theyahia/boxberry-mcp/boxberry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
boxberry 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 10d 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
{
"boxberry": {
"command": "npx",
"args": [
"-y",
"@theyahia/boxberry-mcp"
],
"env": {
"BOXBERRY_API_TOKEN": "YOUR_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.
- 10d ago First seen · 12 lines scan A 0686be6ec320
boxberry is an MCP server published in the GitHub repository theYahia/boxberry-mcp (0 stars, last pushed 5d 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
mindbox
MCP server for Mindbox — CDP, customer profiles, orders, segmentation (Russia). Runs locally from the @theyahia/mindbox-mcp npm package. Needs 2 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.
chestnyznak
MCP server for Chestniy ZNAK — product marking verification, CRPT (Russia). Runs locally from the @theyahia/chestnyznak-mcp npm package.
cdek
MCP server for CDEK delivery API — 16 tools: calculate, orders, courier pickup, tracking, PVZ, print, webhooks. OAuth2 auth. Runs locally from the @theyahia/cdek-mcp npm package. Needs 3 environment variables to run.
retailcrm
MCP server for RetailCRM — orders, customers, inventory, payments, tasks & e-commerce analytics (Russia). Runs locally from the @theyahia/retailcrm-mcp npm package. Needs 2 environment variables to run.
retailcrm-mcp
MCP server for RetailCRM — orders, customers management via API v5. Runs locally from the @theyahia/retailcrm-mcp npm package. Needs 1 environment variable to run.