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/xentral/shiplabel-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/xentral/shiplabel-mcp/shiplabel)<a href="https://agentmods.dev/mcp/xentral/shiplabel-mcp/shiplabel"><img src="https://agentmods.dev/badge/mcp/xentral/shiplabel-mcp/shiplabel/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/xentral/shiplabel-mcp/shiplabel"><img src="https://agentmods.dev/badge/mcp/xentral/shiplabel-mcp/shiplabel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
shiplabel 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
{
"shiplabel": {
"command": "shiplabel-mcp",
"env": {
"DHL_API_CLIENT_ID_SANDBOX": "your-sandbox-app-id",
"DHL_API_CLIENT_SECRET_SANDBOX": "your-sandbox-app-secret",
"SHIPLABEL_DHL_USERNAME": "user-valid",
"SHIPLABEL_DHL_PASSWORD": "SandboxPasswort2023!",
"SHIPLABEL_DHL_ACCOUNTNUMBER": "33333333330102",
"SHIPLABEL_DHL_SANDBOX": "true"
}
}
}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 · 13 lines scan A 4ddd97a75a2f
shiplabel is an MCP server published in the GitHub repository xentral/shiplabel-mcp (1 stars, last pushed 1mo 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
parcel-shipping-rates
Live USPS, UPS and FedEx shipping rates for a US parcel described in plain words. No scale needed. Remote server at quote-api.smklog.com.
smklog-parcel-shipping-rates
MCP server "smklog-parcel-shipping-rates", hosted remotely at quote-api.smklog.com, as configured in smklog/parcel-shipping-rates-mcp.
multi-carrier-tracking-mcp
Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more. Remote server at multi-carrier-tracking-mcp.atlasword.workers.dev.
novaposhta
MCP Server for Nova Poshta API integration with AI assistants. Runs locally from the @shopana/novaposhta-mcp-server npm package. Needs 3 environment variables to run.
novaposhta-http
MCP server "novaposhta-http", hosted remotely at localhost, as configured in shopanaio/carrier-api. Needs 2 environment variables to run.
mcp-shopify-admin
MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts. Runs locally from the mcp-shopify-admin npm package. Needs 9 environment variables to run.