Dockflow
v1.2.2Track containers and shipments in your Dockflow account.
Endpoint health
degraded- Last checked
- 11/20/2026, 8:15:35 AM
- Latency
- 299 ms
- Consecutive failures
- 48
- Endpoint reachable: pass
- Protocol valid: fail
- MCP handshake valid: fail
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.dockflow%2Fmcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
Authentication is required by at least one indexed endpoint or package. No token or secret is included in this configuration.
{
"mcpServers": {
"com.dockflow/mcp": {
"url": "https://mcp.dockflow.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication required
Track a container
track_container
Where is a shipping container now? Looks the container up with its carrier and returns the latest journey: carrier, ports of loading and discharge, departure and arrival dates (actual or estimated), transshipment ports, vessels per leg, and each container's latest confirmed event. Dates are in the local time of the port. Works for any container number, no account needed. A first ask can take up to a minute while the carrier is checked. When the answer has ``status: "checking"``, ask again in a minute with the same number. ``found: false`` means the carrier does not know the container.
Schema valid · SHA-256 c53c804c6294…
View input schema
{ "type": "object", "properties": { "container_number": { "title": "Container Number", "type": "string" } }, "required": [ "container_number" ], "title": "track_containerArguments" }
Connections
streamable-http
https://mcp.dockflow.com/mcp
streamable-http
https://mcp.dockflow.com/public/mcp