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/lxxmng/schedulesmcp-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/lxxmng/schedulesmcp-mcp/ocean-schedules)<a href="https://agentmods.dev/mcp/lxxmng/schedulesmcp-mcp/ocean-schedules"><img src="https://agentmods.dev/badge/mcp/lxxmng/schedulesmcp-mcp/ocean-schedules/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/lxxmng/schedulesmcp-mcp/ocean-schedules"><img src="https://agentmods.dev/badge/mcp/lxxmng/schedulesmcp-mcp/ocean-schedules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ocean-schedules 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 11d 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.
This is a copy
86% identical to mcp-server — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"ocean-schedules": {
"url": "https://mcp.schedulesmcp.com/mcp",
"type": "streamable-http"
}
}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.
- 11d ago First seen · 6 lines scan A bf79e5646dfd
ocean-schedules is an MCP server published in the GitHub repository lxxmng/schedulesmcp-mcp (0 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. It is 86% identical to mcp-server, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
container-tracking
DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts. Remote server at mcp.trackingmcp.com.
searoute
Real shortest sea routes between ports: distance, canals/straits, GeoJSON. UN/LOCODE aware. Runs locally from the @searoute-ts/mcp npm package.
freightutils
Neutral freight reference layer for AI agents: ADR, HS, airlines, UN/LOCODE, ULDs, freight math. Runs locally from the freightutils-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.
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.
shippo-mcp
Multi-carrier shipping for AI agents: compare rates, buy labels, track packages, validate addresses. Remote server at mcp.shippo.com.