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/DCS-Premium-Freight-SRL/claude-for-freightWrote 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/dcs-premium-freight-srl/claude-for-freight/cargowise)<a href="https://agentmods.dev/mcp/dcs-premium-freight-srl/claude-for-freight/cargowise"><img src="https://agentmods.dev/badge/mcp/dcs-premium-freight-srl/claude-for-freight/cargowise/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/dcs-premium-freight-srl/claude-for-freight/cargowise"><img src="https://agentmods.dev/badge/mcp/dcs-premium-freight-srl/claude-for-freight/cargowise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cargowise 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 1mo 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
{
"cargowise": {
"description": "TMS read-only — pull shipment master data, check booking status, log new shipments after booking confirmation. See connectors/cargowise/ for setup.",
"transport": "http",
"url": "REPLACE_WITH_YOUR_CARGOWISE_MCP_URL",
"scope": "project",
"required": false,
"fallback": "Skill outputs the booking confirmation as a draft; operator enters into TMS manually."
}
}What else .mcp.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.
- 1mo ago First seen · 10 lines scan A 7d10b7b85278
cargowise is an MCP server published in the GitHub repository DCS-Premium-Freight-SRL/claude-for-freight (10 stars, last pushed 5mo 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
aura-courier-mcp
Universal Bangladesh courier MCP server — Steadfast, Pathao, RedX & Paperfly with a built-in fraud-risk engine — for Claude, Antigravity, Cursor & n8n AI agents. Runs as a local npx (STDIO) server or a remote HTTP endpoint. Runs locally from the aura-courier-mcp npm package.
novaposhta-http
MCP server "novaposhta-http", hosted remotely at localhost, as configured in shopanaio/carrier-api. Needs 2 environment variables to run.
freightutils
Neutral freight reference layer for AI agents: ADR, HS, airlines, UN/LOCODE, ULDs, freight math. Runs locally from the freightutils-mcp npm package.
marktplaats-mcp
MCP server for Marktplaats.nl and 2dehands.be: search, monitor and manage Dutch and Belgian classifieds from Claude, ChatGPT, Cursor and any MCP client. Runs locally from the marktplaats-mcp Python package. Needs 3 environment variables to run.
woocommerce-mcp
Read-only MCP server for WordPress + WooCommerce products, orders, sales, and posts. Runs locally from the @wppoland/woocommerce-mcp npm package. Needs 3 environment variables to run.
shippo-mcp
MCP server "shippo-mcp", hosted remotely at mcp.shippo.com, as configured in goshippo/ai.