e-Courier MCP by usefulapi
REMOTE · E-COURIER.USEFULAPI.IO
Read delivery orders, quotes, customers, drivers, manifests, invoices and payment records.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://e-courier.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of e-courier.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://e-courier.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/e-courier/ |
| http (plaintext) | http://e-courier.usefulapi.io/mcp | Inconclusive | 302 | http://e-courier.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ecourier_find_customer_by_phone Find customer by phone ~62
Look up a customer by phone number (useful when a caller rings in): id, name and address. GetCustomerInfoFromPhoneNumber.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number, digits (e.g. 7132223333). |
No output schema declared.
No examples provided.
ecourier_get_customer Get customer by id ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Internal customer id. |
No output schema declared.
No examples provided.
ecourier_get_customer_by_code Get customer by code ~53
A customer (billing account) by its e-Courier customer code: id, name and address. GetCustomerByCode.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_code | string | yes | e-Courier customer code. |
No output schema declared.
No examples provided.
ecourier_get_driver Get driver ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_code | string | – | Driver code. |
| driver_id | integer | – | Internal driver id. |
No output schema declared.
No examples provided.
ecourier_get_driver_orders Get a driver's current orders ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_code | string | – | Driver code. |
| driver_phone | string | – | The driver's phone number. |
No output schema declared.
No examples provided.
ecourier_get_driver_skills Get a driver's skills ~56
The skills assigned to one driver, by driver id or driver code (give exactly one). GetDriverSkills.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_code | string | – | Driver code. |
| driver_id | integer | – | Internal driver id. |
No output schema declared.
No examples provided.
ecourier_get_invoice_fees Get invoice fees ~48
The fee lines of one invoice, by invoice id (the id from ecourier_list_invoices). GetInvoiceFees.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | Invoice id. |
No output schema declared.
No examples provided.
ecourier_get_manifest Get manifest ~59
One driver manifest (the route a driver runs for a day) with all its job stops: sequence, addresses, status, pieces and weight. GetManifest.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest_driver_id | integer | yes | The ManifestDriverID of the manifest. |
No output schema declared.
No examples provided.
ecourier_get_order Get order ~172
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. GetJsonOrder.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | The order's Auth (authorization) value. |
| customer_code | string | – | Customer code; useful together with reference. |
| order_id | integer | – | Internal order id. |
| order_number | string | – | The order number shown in e-Courier. |
| reference | string | – | A piece reference / barcode on the order. |
No output schema declared.
No examples provided.
ecourier_get_order_fees Get order fees ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Internal order id (the OrderID from ecourier_get_order). |
No output schema declared.
No examples provided.
ecourier_list_customer_ship_tos List customer ship-to addresses ~78
The saved ship-to (stop) addresses of a customer, by internal customer id, or one ship-to by its id. Give exactly one. GetCustomerShipTo.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | Internal customer id: all its saved addresses. |
| ship_to_id | integer | – | One ship-to address id. |
No output schema declared.
No examples provided.
ecourier_list_driver_manifests List a driver's manifests ~108
The manifests of one driver between two dates, with their job stops. Default status filter is active (A). GetManifestsByDriver.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_id | integer | yes | Internal driver id. |
| end_date | string | yes | Last day, yyyy-mm-dd. |
| manifest_status | string | – | Manifest status code filter (default A). |
| site_id | integer | – | Only this site. |
| start_date | string | yes | First day, yyyy-mm-dd. |
No output schema declared.
No examples provided.
ecourier_list_drivers List active drivers ~51
Every active driver: id, code, name and site. Optionally only one site (multi-site accounts). GetDrivers.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | – | Only drivers of this site id. |
No output schema declared.
No examples provided.
ecourier_list_invoices List invoices ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_end_date | string | – | Last changed to, yyyy-mm-dd. |
| changed_start_date | string | – | Last changed from, yyyy-mm-dd. |
| customer_code | string | – | Only this customer. |
| invoice_end_date | string | yes | Invoice date to, yyyy-mm-dd. Required, at most 31 days after the start. |
| invoice_start_date | string | yes | Invoice date from, yyyy-mm-dd. Required. |
No output schema declared.
No examples provided.
ecourier_list_payments List payments ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_number | string | – | Check number. |
| customer_code | string | – | Only this customer. |
| payment_end_date | string | yes | Payment date to, yyyy-mm-dd. Required, at most 10 days after the start. |
| payment_id | integer | – | One payment id. |
| payment_start_date | string | yes | Payment date from, yyyy-mm-dd. Required. |
No output schema declared.
No examples provided.
ecourier_list_skills List driver skills ~32
The master list of active driver skills (for example HAZMAT) with ids. GetSkills.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ecourier_quote_order Quote an order ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Customer authorization / reference code, if the account uses one. |
| caller | string | – | Name of the person who placed the order. |
| caller_phone | string | – | Phone of the person who placed the order. |
| customer_code | string | yes | e-Courier customer (billing account) code the order is for, as in e-Courier. |
| description | string | – | Order description. |
| other_reference | string | – | Your own reference for the order (PO number etc.). |
| pieces | array | – | The items being moved. Each is linked to the pickup stop and the delivery stop. |
| service | string | – | Service name configured in e-Courier, e.g. Route or Scheduled. |
| stops | array | yes | At least one pickup (P) and one delivery (D) stop, in route order. |
No output schema declared.
No examples provided.
How do I install the e-Courier MCP by usefulapi server?
e-Courier MCP by usefulapi is a hosted endpoint at https://e-courier.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · e-courier.usefulapi.io
claude mcp add --transport http io-usefulapi-e-courier 'https://e-courier.usefulapi.io/mcp'
What is the e-Courier MCP by usefulapi server?
e-Courier MCP by usefulapi is listed in the public MCP registry as io.usefulapi/e-courier. Read delivery orders, quotes, customers, drivers, manifests, invoices and payment records. This page covers its hosted endpoint (https://e-courier.usefulapi.io/mcp).
Is the e-Courier MCP by usefulapi server safe to use?
e-Courier MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the e-Courier MCP by usefulapi server expose?
e-Courier MCP by usefulapi exposes 17 tools: ecourier_get_order, ecourier_get_order_fees, ecourier_quote_order, ecourier_get_customer_by_code, ecourier_get_customer, and 12 more. Their descriptions and schemas cost roughly 1,542 tokens of context every time the server is loaded.
Does the e-Courier MCP by usefulapi server require authentication?
Its publisher declares no required credentials for e-Courier MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the e-Courier MCP by usefulapi server still maintained?
e-Courier MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the e-Courier MCP by usefulapi server?
VerifyMCP ran 4 checks on e-Courier MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about e-Courier MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.