Order from a shop, pay in USDC over x402, and get the QR to collect in person.
e-Courier MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read delivery orders, quotes, customers, drivers, manifests, invoices and payment records.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http e-courier-mcp-by-usefulapi https://e-courier.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# ecourier_get_order, ecourier_get_order_fees, ecourier_quote_order and 14 more
e-Courier MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http e-courier-mcp-by-usefulapi https://e-courier.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
One delivery order with everything e-Courier holds: status (N new, A assigned, X deleted), customer, stops and their pickup/delivery times and POD names, pieces, jobs and drivers, fees, events and notifications. Give exactly one of order_number, order_id, auth (the customer's authorization code) or reference (a piece reference; add customer_code to narrow it). Signature images are not returned. Ge
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | no | The order number shown in e-Courier. |
| order_id | integer | no | Internal order id. |
| auth | string | no | The order's Auth (authorization) value. |
| reference | string | no | A piece reference / barcode on the order. |
| customer_code | string | no | Customer code; useful together with reference. |
The fee lines (what was charged for the delivery: base rate, fuel, waiting time and so on) of one order, by internal order id. GetOrderFees.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | Internal order id (the OrderID from ecourier_get_order). |
Price and availability for a delivery WITHOUT creating it: e-Courier applies the customer's rates to the stops and pieces and returns the order with the quoted amount. Supply a customer code, pickup/delivery stops and optional pieces. Nothing is saved and nobody is notified. QuoteOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_code | string | yes | e-Courier customer (billing account) code the order is for, as in e-Courier. |
| service | string | no | Service name configured in e-Courier, e.g. Route or Scheduled. |
| caller | string | no | Name of the person who placed the order. |
| caller_phone | string | no | Phone of the person who placed the order. |
| description | string | no | Order description. |
| other_reference | string | no | Your own reference for the order (PO number etc.). |
| auth | string | no | Customer authorization / reference code, if the account uses one. |
| pieces | array | no | The items being moved. Each is linked to the pickup stop and the delivery stop. |
| stops | array | yes | At least one pickup (P) and one delivery (D) stop, in route order. |
A customer (billing account) by its e-Courier customer code: id, name and address. GetCustomerByCode.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_code | string | yes | e-Courier customer code. |
The full customer record by internal customer id: contact, address, credit status and limit, balance, billing settings. Card numbers and passwords are never returned. GetCustomerById.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Internal customer id. |
Look up a customer by phone number (useful when a caller rings in): id, name and address. GetCustomerInfoFromPhoneNumber.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | Phone number, digits (e.g. 7132223333). |
The saved ship-to (stop) addresses of a customer, by internal customer id, or one ship-to by its id. Give exactly one. GetCustomerShipTo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | no | Internal customer id: all its saved addresses. |
| ship_to_id | integer | no | One ship-to address id. |
Every active driver: id, code, name and site. Optionally only one site (multi-site accounts). GetDrivers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | integer | no | Only drivers of this site id. |
Driver records with their vehicles and file names (never SSN or tax ids). With driver_id or driver_code one driver; with neither, every active and inactive driver. GetDriver.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_id | integer | no | Internal driver id. |
| driver_code | string | no | Driver code. |
What a driver is carrying right now: the open orders on the driver's manifest (customer, pickup and delivery names, delivery zip, ready and due times), found by driver code or by the driver's phone number. Give exactly one. GetDriverInfoFromDriverCode / GetDriverInfoFromDriverPhone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_code | string | no | Driver code. |
| driver_phone | string | no | The driver's phone number. |
The master list of active driver skills (for example HAZMAT) with ids. GetSkills.
No parameter schema on file.
The skills assigned to one driver, by driver id or driver code (give exactly one). GetDriverSkills.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_id | integer | no | Internal driver id. |
| driver_code | string | no | Driver code. |
One driver manifest (the route a driver runs for a day) with all its job stops: sequence, addresses, status, pieces and weight. GetManifest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest_driver_id | integer | yes | The ManifestDriverID of the manifest. |
The manifests of one driver between two dates, with their job stops. Default status filter is active (A). GetManifestsByDriver.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driver_id | integer | yes | Internal driver id. |
| start_date | string | yes | First day, yyyy-mm-dd. |
| end_date | string | yes | Last day, yyyy-mm-dd. |
| site_id | integer | no | Only this site. |
| manifest_status | string | no | Manifest status code filter (default A). |
Invoices in an invoice date range (invoice_start_date and invoice_end_date are both required, at most 31 days apart: e-Courier rejects anything else). Optionally narrow by customer code and by a last-changed range. GetInvoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_start_date | string | yes | Invoice date from, yyyy-mm-dd. Required. |
| invoice_end_date | string | yes | Invoice date to, yyyy-mm-dd. Required, at most 31 days after the start. |
| changed_start_date | string | no | Last changed from, yyyy-mm-dd. |
| changed_end_date | string | no | Last changed to, yyyy-mm-dd. |
| customer_code | string | no | Only this customer. |
The fee lines of one invoice, by invoice id (the id from ecourier_list_invoices). GetInvoiceFees.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | integer | yes | Invoice id. |
Customer payments received in a payment date range (payment_start_date and payment_end_date are both required, at most 10 days apart: e-Courier rejects anything else). Optionally narrow by customer code, check number or payment id. GetPayment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_start_date | string | yes | Payment date from, yyyy-mm-dd. Required. |
| payment_end_date | string | yes | Payment date to, yyyy-mm-dd. Required, at most 10 days after the start. |
| customer_code | string | no | Only this customer. |
| check_number | string | no | Check number. |
| payment_id | integer | no | One payment id. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install e-Courier MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ecourier_get_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_order_fees | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_quote_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_customer_by_code | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_find_customer_by_phone | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_customer_ship_tos | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_drivers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_driver | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_driver_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_skills | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_driver_skills | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_manifest | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_driver_manifests | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_get_invoice_fees | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ecourier_list_payments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.9.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish e-Courier MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.