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/DeviceIngineering/wb-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/deviceingineering/wb-mcp-server/wb-mcp-server)<a href="https://agentmods.dev/mcp/deviceingineering/wb-mcp-server/wb-mcp-server"><img src="https://agentmods.dev/badge/mcp/deviceingineering/wb-mcp-server/wb-mcp-server/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/deviceingineering/wb-mcp-server/wb-mcp-server"><img src="https://agentmods.dev/badge/mcp/deviceingineering/wb-mcp-server/wb-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wb-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 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
{
"wb-mcp-server": {
"command": "uvx",
"args": [
"wb-mcp-server"
],
"env": {
"WB_API_TOKEN": "",
"DATA_DIR": ""
}
}
}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 · 12 lines scan A 5788599cedff
wb-mcp-server is an MCP server published in the GitHub repository DeviceIngineering/wb-mcp-server (3 stars, last pushed 3d 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
ozon-mcp-server
MCP server for Ozon Seller API + Performance API: 151 tools for prices, promos, ads, orders, returns and finance. Runs locally from the ozon-mcp-server Python package. Needs 5 environment variables to run.
ozon
MCP server "ozon", hosted remotely at localhost, as configured in DeviceIngineering/ozon-mcp-server.
bounty-api
Singapore property & financial data APIs for AI agents. 27 MCP tools. x402 micropayments. Runs locally from the bountyapi-mcp npm package. Needs 1 environment variable to run.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.
mcp-epayco
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks. Runs locally from the @codespar/mcp-epayco npm package. Needs 3 environment variables to run.
mcp-braspag
MCP server for Braspag — Cielo orchestration, token vault (Cartão Protegido), recurrence, split. Runs locally from the @codespar/mcp-braspag npm package. Needs 3 environment variables to run.