Locate2u MCP by usefulapi
REMOTE · LOCATE2U.USEFULAPI.IO
Read stops, orders, trips and ratings; add notes to stops and shipments in Locate2u.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
- 2 Nov 26 −45
- 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 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 62
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 5 Nov 2026 · Probed https://locate2u.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 locate2u.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://locate2u.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/locate2u/ |
| http (plaintext) | http://locate2u.usefulapi.io/mcp | Inconclusive | 302 | http://locate2u.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 →
locate2u_add_shipment_note Add a note to a shipment ~92
WRITE: add a text note to a shipment, optionally tied to one of its stops. Each call adds a new note (do not retry blindly). Locate2u API: POST /shipments/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | The note text. |
| shipment_id | integer | yes | – |
| stop_id | integer | – | A stop of the shipment the note belongs to. |
No output schema declared.
No examples provided.
locate2u_add_stop_note Add a note to a stop ~76
WRITE: add a text note to a stop. It is visible to the team and the driver. Each call adds a new note (do not retry blindly). Locate2u API: POST /stops/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | The note text. |
| stop_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_find_order Find an order by reference ~61
Find a single order by its order number, or by a source and source reference pair. Locate2u API: GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | – | – |
| source | string | – | – |
| source_reference | string | – | – |
No output schema declared.
No examples provided.
locate2u_get_customer Get a customer ~47
Get one customer by id. Locate2u API: GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | The customerId (from locate2u_list_customers). |
No output schema declared.
No examples provided.
locate2u_get_driver_trip Get a driver's trip for a day ~78
Get the trip of one team member on a day, optionally filtered by status. Locate2u API: GET /trips/user/{publicUserId}/{tripDate}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_lines | boolean | – | – |
| public_user_id | string | yes | – |
| status | string | – | – |
| trip_date | string | yes | – |
No output schema declared.
No examples provided.
locate2u_get_item Get an inventory item ~37
Get one inventory item by id. Locate2u API: GET /items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_get_me Get the current user ~39
Get the user that owns the connected app: name, email, role, time zone. Locate2u API: GET /users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locate2u_get_order Get an order ~39
Get one order by id. Locate2u API: GET /orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | The order id. |
No output schema declared.
No examples provided.
locate2u_get_shipment Get a shipment ~64
Get a shipment with its pickup and drop stops and items. Locate2u API: GET /shipments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_cost_and_charge_lines | boolean | – | – |
| include_tracking_link | boolean | – | – |
| shipment_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_get_stop Get a stop ~78
Get one stop (a delivery or pickup) with status, contact, address and time window. Locate2u API: GET /stops/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_items | boolean | – | – |
| include_lines | boolean | – | – |
| include_tracking_link | boolean | – | – |
| stop_id | integer | yes | The stopId. |
No output schema declared.
No examples provided.
locate2u_get_stop_pod_answers Get proof-of-delivery answers of a stop ~55
Get the answers a driver gave to the proof-of-delivery questions on a stop. Locate2u API: GET /stops/{id}/podquestionanswers.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_get_team Get the team ~30
Get the connected team with its settings and branding. Locate2u API: GET /team.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locate2u_get_team_member Get a team member ~58
Get one team member by public user id. Locate2u API: GET /team-members/{publicUserId}.
| Name | Type | Req | Description |
|---|---|---|---|
| public_user_id | string | yes | The member's publicUserId (from locate2u_list_team_members). |
No output schema declared.
No examples provided.
locate2u_get_team_trips_summary Summarize the team's trips for a day ~58
Summary of every trip in the team on a day: driver, distance, time, stop counts, status. Locate2u API: GET /team/trips/{tripDate}.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_date | string | yes | – |
No output schema declared.
No examples provided.
locate2u_get_trip Get a trip by id ~49
Get one trip by id with its stops. Locate2u API: GET /trips/id/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_lines | boolean | – | – |
| trip_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_list_customer_ratings List delivery ratings ~95
Delivery ratings that customers left for the team's stops over a date range. Locate2u API: GET /team/{teamId}/customer-ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| higher_ratings | boolean | – | – |
| lower_ratings | boolean | – | – |
| start_date | string | yes | – |
| team_id | integer | yes | The team id (from locate2u_get_team). |
No output schema declared.
No examples provided.
locate2u_list_customers List customers ~26
List the team's customers. Locate2u API: GET /customers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locate2u_list_orders_created List orders created in a date range ~98
List orders created between two dates, optionally with stops and items. Locate2u API: GET /orders/created.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start date yyyy-mm-dd. |
| include_order_items | boolean | – | – |
| include_order_lines | boolean | – | – |
| include_stop_items | boolean | – | – |
| include_stops | boolean | – | – |
| to_date | string | yes | End date yyyy-mm-dd. |
No output schema declared.
No examples provided.
locate2u_list_runs List runs for a day ~74
List the runs scheduled for a day, optionally for one team member, customer or run number. Locate2u API: GET /runs/{tripDate}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | – |
| run_number | string | – | – |
| team_member | string | – | – |
| trip_date | string | yes | – |
No output schema declared.
No examples provided.
locate2u_list_scheduled_stops List scheduled stops ~88
List stops scheduled for a day (default: today in the team's zone), with paging. Locate2u API: GET /stops/scheduled.
| Name | Type | Req | Description |
|---|---|---|---|
| include_shipments | boolean | – | – |
| skip | integer | – | – |
| take | integer | – | – |
| team_region_id | integer | – | – |
| trip_date | string | – | Day yyyy-mm-dd. |
No output schema declared.
No examples provided.
locate2u_list_services List services ~27
List all services the team offers. Locate2u API: GET /services.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locate2u_list_shipment_notes List notes of a shipment ~42
List all notes on a shipment. Locate2u API: GET /shipments/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| shipment_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_list_stop_notes List notes of a stop ~44
List all notes on a stop, with attachments. Locate2u API: GET /stops/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_id | integer | yes | – |
No output schema declared.
No examples provided.
locate2u_list_team_members List team members ~75
List the drivers and staff in the team, optionally with their current location. Locate2u API: GET /team-members.
| Name | Type | Req | Description |
|---|---|---|---|
| include_current_location | boolean | – | Include each member's last known location. |
| team_region_id | integer | – | Only members of this region (from locate2u_list_team_regions). |
No output schema declared.
No examples provided.
locate2u_list_team_regions List team regions ~30
List the regions of the team. Locate2u API: GET /team-regions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locate2u_list_team_trips List all trips of the team for a day ~54
All trips (assigned and unassigned) for a day, each with its driver and stops. Locate2u API: GET /trips/team/{tripDate}.
| Name | Type | Req | Description |
|---|---|---|---|
| trip_date | string | yes | – |
No output schema declared.
No examples provided.
locate2u_list_unassigned_shipments List unassigned shipments ~64
List shipments that no team member has yet. Locate2u API: GET /shipments/unassigned.
| Name | Type | Req | Description |
|---|---|---|---|
| pickup_within_km_distance | number | – | – |
| team_region_id | integer | – | – |
| trip_date | string | – | – |
No output schema declared.
No examples provided.
locate2u_list_unassigned_stops List unassigned stops ~60
List stops that no driver has yet. Locate2u API: GET /stops/unassigned.
| Name | Type | Req | Description |
|---|---|---|---|
| include_shipments | boolean | – | – |
| team_region_id | integer | – | – |
| trip_date | string | – | – |
No output schema declared.
No examples provided.
locate2u_list_warehouses List warehouses ~42
List the team's warehouses. Locate2u API: GET /warehouses.
| Name | Type | Req | Description |
|---|---|---|---|
| team_region_id | integer | – | Only warehouses of this region. |
No output schema declared.
No examples provided.
locate2u_search_customers Search customers ~72
Search customers by text (name, company, email, phone). Locate2u API: GET /customers/search.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (starts at 1). |
| per_page | integer | – | Results per page. |
| search_text | string | yes | Text to search for. |
No output schema declared.
No examples provided.
locate2u_search_items Search inventory items ~87
Search inventory items by keyword, warehouse or status. Locate2u API: GET /items/search.
| Name | Type | Req | Description |
|---|---|---|---|
| item_status | string | – | – |
| keyword | string | – | – |
| location_status | string | – | – |
| page | integer | – | Page number (starts at 1). |
| per_page | integer | – | Results per page. |
| warehouse_id | integer | – | – |
No output schema declared.
No examples provided.
locate2u_search_orders Search orders ~122
Search orders by order number, purchase order number, status, payment status, customer or date. Locate2u API: GET /orders/search.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | – |
| order_date | string | – | Order date yyyy-mm-dd. |
| order_number | string | – | – |
| page | integer | – | Page number (starts at 1). |
| payment_status | string | – | Payment status. |
| per_page | integer | – | Results per page. |
| purchase_order_number | string | – | – |
| status | string | – | Order status. |
No output schema declared.
No examples provided.
locate2u_search_stops Find stops by source reference ~69
Find stops by the source reference that the integration stored on them. Locate2u API: GET /stops/search.
| Name | Type | Req | Description |
|---|---|---|---|
| include_items | boolean | – | – |
| include_lines | boolean | – | – |
| include_tracking_link | boolean | – | – |
| source_reference | string | yes | – |
No output schema declared.
No examples provided.
locate2u_team_travel_statistics Team travel statistics ~69
Distance and time driven by the team's members and asset groups over a date range. Locate2u API: GET /team/reports/travel-statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | – |
| team_region_id | integer | – | – |
| to_date | string | – | – |
No output schema declared.
No examples provided.
How do I install the Locate2u MCP by usefulapi server?
Locate2u MCP by usefulapi is a hosted endpoint at https://locate2u.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 · locate2u.usefulapi.io
claude mcp add --transport http io-usefulapi-locate2u 'https://locate2u.usefulapi.io/mcp'
What is the Locate2u MCP by usefulapi server?
Locate2u MCP by usefulapi is listed in the public MCP registry as io.usefulapi/locate2u. Read stops, orders, trips and ratings; add notes to stops and shipments in Locate2u. This page covers its hosted endpoint (https://locate2u.usefulapi.io/mcp).
Is the Locate2u MCP by usefulapi server safe to use?
Locate2u 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 Locate2u MCP by usefulapi server expose?
Locate2u MCP by usefulapi exposes 34 tools: locate2u_get_me, locate2u_get_team, locate2u_list_team_members, locate2u_get_team_member, locate2u_list_team_regions, and 29 more. Their descriptions and schemas cost roughly 2,099 tokens of context every time the server is loaded.
Does the Locate2u MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Locate2u 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 Locate2u MCP by usefulapi server still maintained?
Locate2u MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Locate2u MCP by usefulapi server?
VerifyMCP ran 4 checks on Locate2u 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 Locate2u 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.