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/shopanaio/carrier-apiWrote 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/shopanaio/carrier-api/novaposhta-http)<a href="https://agentmods.dev/mcp/shopanaio/carrier-api/novaposhta-http"><img src="https://agentmods.dev/badge/mcp/shopanaio/carrier-api/novaposhta-http/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/shopanaio/carrier-api/novaposhta-http"><img src="https://agentmods.dev/badge/mcp/shopanaio/carrier-api/novaposhta-http.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
novaposhta-http 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
{
"novaposhta-http": {
"type": "http",
"url": "http://localhost:3000/mcp",
"env": {
"NOVA_POSHTA_API_KEY": "your_api_key_here",
"LOG_LEVEL": "info"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 9d ago First seen · 10 lines scan A fcfc7ec9a444
novaposhta-http is an MCP server published in the GitHub repository shopanaio/carrier-api (7 stars, last pushed 21d 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
mcp-yango-delivery
MCP server for the Yango Delivery claims B2B API: price checks, delivery claims, courier tracking. Runs locally from the mcp-yango-delivery npm package. Needs 5 environment variables to run.
mcp-yandex-dostavka
MCP server for the Yandex Delivery B2B API: express claims, tracking, NDD/pickup-point orders. Runs locally from the mcp-yandex-dostavka npm package. Needs 8 environment variables to run.
mcp-odoo
Odoo MCP for AI agents — 41 tools, gated writes, multi-instance. Free hosted product: ERPipe (mcp.erpipe.com). Runs locally from the odoo-mcp Python package. Needs 4 environment variables to run.
marketplaces-mcp-ru
MCP servers for Wildberries and Ozon Seller APIs (schema-driven, safety-gated). Runs locally from the marketplaces-mcp-ru Python package. Needs 5 environment variables to run.
sfcc-dev-mcp
MCP server for Salesforce B2C Commerce Cloud development assistance. Runs locally from the sfcc-dev-mcp npm package.
ecommerce
Product and category demand trend volume over time, with growth signals. Free key at trendsmcp.ai. Remote server at ecommerce.api.trendsmcp.ai.