CXT Software MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 14 tools. Last commit 26 Oct 2026.
Track and search CXT courier orders, check drivers, propose and save order and route plans.
Uptime history
31 hours of history
31 hours agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
323 ms
Response time
average over 24h
0
Stars
last commit 26 Oct 2026
What changed 4
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.
25 Oct
a tool changed version4 times that day
and 3 more, back to 25 October 2026
Nothing serious here today
Today is the operative word: we check CXT Software MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add cxt-software --transport http https://cxt-software.usefulapi.io/mcpSettings → Connectors → Add custom connector, then paste this address
https://cxt-software.usefulapi.io/mcp~/.codex/config.toml
[mcp_servers.cxt-software]
url = "https://cxt-software.usefulapi.io/mcp".cursor/mcp.json
{
"mcpServers": {
"cxt-software": {
"url": "https://cxt-software.usefulapi.io/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"cxt-software": {
"type": "http",
"url": "https://cxt-software.usefulapi.io/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
cxt
cxt_get_dispatch_order
One on-demand order with itemized charges, as an OPERATIONS APP (X Dispatch) user sees it (sign in with user type XDISPATCH): addresses, times, driver, status events, proof of delivery. Costs 1 API credit with the vendor. GET /v2/Dispatch/Orders/{onDemandOrderId}.
cxt_get_order
One on-demand order with its status, confirmation, pickup, delivery and proof-of-delivery details, as an INTERNET user sees it (sign in with user type INET). Optionally with the itemized charges. Operations App users should use cxt_get_dispatch_order. Costs 1 API credit with the vendor. GET /v2/Orders/{orderId}/{includeItemizedCharges}.
cxt_get_planning_limits
The itinerary planning limits of this X Dispatch system: maxAllowedStops (shipments x 2), maxAllowedLocations and maxAllowedPlaceholders. Needs an Operations App user with the ITINERARY_PLANNING_ACCESS permission. GET /v3/ItineraryPlanning/Settings.
cxt_list_recent_orders
The most recent orders of the signed-in INTERNET user (user type INET; the orders of their account). Costs 1 API credit with the vendor. POST /v2/Shipments/Summaries with numRecentOrders.
cxt_optimize_order_plan
Re-optimize a single driver's plan after manual changes (proposal only: nothing is dispatched until cxt_save_order_plan). Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Orders/Optimize.
cxt_optimize_route_plan
Re-optimize a single route after manual changes (proposal only: nothing changes until cxt_save_route_plan). Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Routes/{postDate}/Optimize.
cxt_plan_orders
Generate a proposed itinerary that assigns on-demand orders to drivers (pickup and delivery stops in sequence, with times, distance and unassigned stops). This only PROPOSES a plan: nothing is dispatched until cxt_save_order_plan is called. Needs ITINERARY_PLANNING_ACCESS. Check the limits with cxt_get_planning_limits first. POST /v3/ItineraryPlanning/Orders.
cxt_plan_routes
Generate a proposed re-sequencing of the stops of existing routes for one route date (stops move between the output routes, with times, distance and unassigned stops). Proposal only: nothing changes until cxt_save_route_plan is called. Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Routes/{postDate}.
cxt_save_order_plan
COMMIT an order plan: assigns the orders to the drivers and DISPATCHES them (drivers receive the work in the driver app; customers may be notified by the system's own status rules). Use only after the user has seen and approved the plan from cxt_plan_orders / cxt_optimize_order_plan. Pass each driver's stops from the plan reply: id, type (PICKUP or DELIVERY), sequence and from (the scheduled time). Response is empty on success (204). Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Orders/Save.
cxt_save_route_plan
COMMIT a route plan for one route date: moves and re-sequences route stops as in the plan and DISPATCHES the changed routes to drivers. Use only after the user has seen and approved the plan from cxt_plan_routes / cxt_optimize_route_plan. Pass each route's stops from the plan reply: id, sequence and from (the scheduled time). Response is empty on success (204). Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Routes/{postDate}/Save.
cxt_search_shipments
Search orders and route stops by place, address, city, state, postal code, order template, or only by date range. tracking_type says which field search_criteria is matched against: Location (origin/destination or stop name), Address, City, State, Postal (zip or zip+4), Template (order template name), Tracking (references/barcodes) or DateOnly (no criteria: everything between begin_date and end_date). Returns shipment summaries, up to 1000 per page. An INET login sees the most detail; with an Operations App login this endpoint is called without credentials (CXT lists only internet users and anonymous callers for it), so the view is limited. Costs 1 API credit with the vendor. POST /v2/Shipments/Summaries.
cxt_track_shipments
Track orders and route stops by tracking number: matches a parcel reference, a parcel item barcode, or Reference1/Reference2 of an order or route stop. Returns shipment summaries with status events and proof of delivery as far as the caller's permissions allow: an INET login sees the most detail; with an Operations App login this endpoint is called without credentials (CXT lists only internet users and anonymous callers for it), which returns the limited public tracking view. Costs 1 API credit with the vendor. POST /v2/Shipments/Summaries.
cxt_validate_driver_for_orders
Check one driver against specific orders: vehicle violations, HR violations and capability violations (for example Hazmat or Lift Gate that the driver lacks). Changes nothing. Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Orders/Drivers/{driverId}/Validate.
cxt_validate_drivers
Check whether drivers are available to be planned: for each driver id, vehicle violations (for example an expired inspection) and HR violations (for example not scheduled), each with isBypassable. Changes nothing. Needs ITINERARY_PLANNING_ACCESS. POST /v3/ItineraryPlanning/Orders/Drivers/Validate.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://cxt-software.usefulapi.io/mcp | streamable-http | answering | 218 ms | 14 min ago |
Alternatives to CXT Software MCP by usefulapi
same job, measured the same wayOptimoRoute MCP by usefulapi
by usefulapi
Check OptimoRoute routes, orders and driver events, and create orders or start route planning.
Track-POD MCP by usefulapi
by usefulapi
Read Track-POD orders, routes, drivers, vehicles and proof of delivery; create orders.
Spoke Dispatch MCP by usefulapi
by usefulapi
Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.
Upper Route Planner MCP by usefulapi
by usefulapi
Read Upper drivers and stops; create and optimize routes, assign drivers, share routes to the app.
Shipday MCP by usefulapi
by usefulapi
Read Shipday orders, carriers and delivery status; create orders and assign drivers.
Withvibe Roadmap
by withvibe
Per-env roadmap board for WithVibe — an MCP server the orchestrator drives to plan and track work.
Pipedrive MCP by usefulapi
by usefulapi
Read deals, persons, organizations, activities and pipelines; create and update CRM records.
Leclerc Drive
by skunkobi
MCP server for E.Leclerc Drive — search products, manage cart, and order groceries from Claude
CXT Software MCP by usefulapi — questions
Answers built from our own checks of this server.
What can CXT Software MCP by usefulapi do?
It exposes 14 tools, read directly from the server on our last check. Among them: cxt_get_dispatch_order, cxt_get_order, cxt_get_planning_limits, cxt_list_recent_orders, cxt_optimize_order_plan, cxt_optimize_route_plan and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is CXT Software MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 323 ms. The bar chart above shows every period we have measured.
How do I connect CXT Software MCP by usefulapi?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does CXT Software MCP by usefulapi need an API key?
No. CXT Software MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is CXT Software MCP by usefulapi?
It answers our handshake in 323 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is CXT Software MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at cxt-software.usefulapi.io, which runs on its operator's own terms.