Track-POD MCP by usefulapi
by track-pod.usefulapi.io in Other
Read Track-POD orders, routes, drivers, vehicles and proof of delivery; create orders.
https://track-pod.usefulapi.io/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 374 ms typical, 404 ms slowest 5%
- Last check
- 9 min ago
- Next check
- in 6 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"track-pod-mcp-by-usefulapi": {
"type": "http",
"url": "https://track-pod.usefulapi.io/mcp"
}
}
}16 tools
- trackpod_list_orders
List the orders of one day — by order date (GET /Order/Date/{date}) or by planned route date (GET /Order/Route/Date/{date}) — with optional filters on delivery status, driver and route number. Track-POD returns the whole day at once; this tool pages it (offset/limit) and reports
- trackpod_list_orders_changed_since
List orders whose delivery status changed after a moment in the last 24 hours (GET /Order/Status/Date/{date-time}; Track-POD accepts no earlier time than UTC now − 1 day). Good for 'what was delivered / failed since this morning'. Paged here (offset/limit).
- trackpod_list_route_orders
List the orders on one route, in route order, by route code (GET /Order/Route/Code/{code}). Paged here (offset/limit).
- trackpod_get_order
Get one order with every field: client, address, time slot, goods lines, route, driver, delivery status, ETA, signature/photo links and tracking link. Pass exactly one of number, order_id or track_id (GET /Order/Number|Id|TrackId/{…}). A removed order answers with who removed it
- trackpod_find_orders_by_number
List the last 25 orders that share one order number (re-deliveries, repeated jobs) — GET /Order/Number/{number}/List. Use it when an order number was reused and trackpod_get_order returns only one of them.
- trackpod_get_proof_of_delivery
Get the electronic proof of delivery (ePOD) of one order: status and status time/GPS, who signed, signature and photo links (valid 24 h), driver comment, reject reasons, delivered vs ordered goods quantities, cash collected, customer feedback and the PDF delivery-note link (Repor
- trackpod_list_reject_reasons
List the account's reasons for not delivering / not collecting: site, order, goods and scanning issues (GET /RejectReason).
- trackpod_list_routes
List the routes of one day (GET /Route/Date/{date}): code, status (Draft, Ready, Loaded, InProgress, Closed), driver, vehicle, planned vs actual start/finish, distance, cost, current GPS position, and per-route order counts by status. Paged here (offset/limit).
- trackpod_get_route
Get one route with its status, driver, vehicle, timings, distance, cost, current GPS position and its orders. Pass exactly one of route_code or route_id (GET /Route/Code|Id/{…}).
- trackpod_get_route_track
Get the driver's recorded GPS track of a route (latitude, longitude, speed in m/s, time) — GET /Route/Track/Code|Id/{…}. Pass exactly one of route_code or route_id. Points are paged here (offset/limit, max 1000 per call).
- trackpod_list_drivers
List the account's drivers: name, username, phone, vehicle, depot, zone, teams and active flag (GET /Driver). Paged here.
- trackpod_get_driver
Get one driver by Track-POD id (UUID) or by username (GET /Driver/Id/{id} or /Driver/Username/{username}). Pass exactly one.
- trackpod_list_vehicles
List the account's vehicles: plate number, assigned driver, depot, capacity (weight/volume/pallets/size), limits, costs, type and carrier (GET /Vehicle, optional plate-number filter). Paged here.
- trackpod_get_vehicle
Get one vehicle by its Track-POD id (an integer, from trackpod_list_vehicles) — GET /Vehicle/{id}.
- trackpod_list_vehicle_checks
Driver vehicle inspections (before/after route): checklist items with pass/fail, notes, photo links (valid 24 h), odometer and signature. date only: every check of that day (GET /VehicleCheck/Date/{date}); date + vehicle_number: that vehicle's checks of the day; vehicle_number on
- trackpod_create_order
Create ONE REAL unscheduled order in Track-POD (POST /Order): a delivery or a collection for a client at an address, ready to be planned into a route by a dispatcher. It does not create or optimise routes. Depending on the account's notification settings the customer may later re
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 min ago | Passed | 200 | 404 ms |
| 9 h ago | Passed | 200 | 344 ms |
| 18 h ago | Passed | 200 | 434 ms |
| 28 h ago | Passed | 200 | 374 ms |
| 38 h ago | Passed | 200 | 332 ms |