No user-submitted related servers found.
Scored across 125 tools
Several tool clusters are nearly interchangeable: search_consignments overlaps with get_consignments_by_reference1/reference2/carrier_id, get_item_labels_zip and return_item_pdfs_for_consignments both return item-label zips, and the location-search tools have fuzzy boundaries. Descriptions help in places, but with 125 tools an agent will frequently struggle to pick the right variant.
All tools share the machship_ prefix and mostly follow verb_noun snake_case (get_consignment, create_quote, delete_identities). However, there are odd deviations like machship_ping, attempt_auto_reconciliation, return_item_pdfs_for_consignments, and update_reprice_consignment, and numbered reference variants (reference1/reference2) are inconsistently stylised.
125 tools is an extreme count for a single MCP server. Even though the freight domain is broad, many endpoints are redundant variants (same resource with/without complex items, POST vs GET variants, multiple lookup-by-reference tools), creating a heavy, hard-to-navigate surface.
The core consignment workflow is remarkably complete: create/get/edit/delete/list consignments, pending consignments, quotes, routes, manifests, labels, attachments, items, identities, and org links are all present. The main gaps are secondary lifecycle operations such as updating pending consignments, updating/deleting quotes, and creating/updating standard (non-complex) items.