# Locate2u MCP by usefulapi (remote · locate2u.usefulapi.io)

Read stops, orders, trips and ratings; add notes to stops and shipments in Locate2u.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `locate2u.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u.md), [page](https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u)

## Channel facts

- Endpoint: `https://locate2u.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-locate2u 'https://locate2u.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-locate2u": {
      "url": "https://locate2u.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-locate2u": {
      "type": "http",
      "url": "https://locate2u.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-locate2u]
url = "https://locate2u.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-locate2u": {
      "type": "remote",
      "url": "https://locate2u.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-locate2u --url 'https://locate2u.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-locate2u:
    url: "https://locate2u.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-locate2u": {
      "Transport": "http",
      "Url": "https://locate2u.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-locate2u -t streamable-http -u 'https://locate2u.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-locate2u": {
      "type": "http",
      "url": "https://locate2u.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 62)

First indexed and scored.

## MCP tools (34)

### `locate2u_get_me` (~39 tokens)

Get the current user

Get the user that owns the connected app: name, email, role, time zone. Locate2u API: GET /users/me.

### `locate2u_get_team` (~30 tokens)

Get the team

Get the connected team with its settings and branding. Locate2u API: GET /team.

### `locate2u_list_team_members` (~75 tokens)

List team members

List the drivers and staff in the team, optionally with their current location. Locate2u API: GET /team-members.

Input parameters:

- `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).

### `locate2u_get_team_member` (~58 tokens)

Get a team member

Get one team member by public user id. Locate2u API: GET /team-members/{publicUserId}.

Input parameters:

- `public_user_id` (string, required): The member's publicUserId (from locate2u_list_team_members).

### `locate2u_list_team_regions` (~30 tokens)

List team regions

List the regions of the team. Locate2u API: GET /team-regions.

### `locate2u_list_warehouses` (~42 tokens)

List warehouses

List the team's warehouses. Locate2u API: GET /warehouses.

Input parameters:

- `team_region_id` (integer): Only warehouses of this region.

### `locate2u_list_services` (~27 tokens)

List services

List all services the team offers. Locate2u API: GET /services.

### `locate2u_list_customers` (~26 tokens)

List customers

List the team's customers. Locate2u API: GET /customers.

### `locate2u_search_customers` (~72 tokens)

Search customers

Search customers by text (name, company, email, phone). Locate2u API: GET /customers/search.

Input parameters:

- `page` (integer): Page number (starts at 1).
- `per_page` (integer): Results per page.
- `search_text` (string, required): Text to search for.

### `locate2u_get_customer` (~47 tokens)

Get a customer

Get one customer by id. Locate2u API: GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): The customerId (from locate2u_list_customers).

### `locate2u_search_orders` (~122 tokens)

Search orders

Search orders by order number, purchase order number, status, payment status, customer or date. Locate2u API: GET /orders/search.

Input parameters:

- `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.

### `locate2u_get_order` (~39 tokens)

Get an order

Get one order by id. Locate2u API: GET /orders/{id}.

Input parameters:

- `order_id` (integer, required): The order id.

### `locate2u_find_order` (~61 tokens)

Find an order by reference

Find a single order by its order number, or by a source and source reference pair. Locate2u API: GET /orders.

Input parameters:

- `order_number` (string)
- `source` (string)
- `source_reference` (string)

### `locate2u_list_orders_created` (~98 tokens)

List orders created in a date range

List orders created between two dates, optionally with stops and items. Locate2u API: GET /orders/created.

Input parameters:

- `from_date` (string, required): Start date yyyy-mm-dd.
- `include_order_items` (boolean)
- `include_order_lines` (boolean)
- `include_stop_items` (boolean)
- `include_stops` (boolean)
- `to_date` (string, required): End date yyyy-mm-dd.

### `locate2u_get_stop` (~78 tokens)

Get a stop

Get one stop (a delivery or pickup) with status, contact, address and time window. Locate2u API: GET /stops/{id}.

Input parameters:

- `include_items` (boolean)
- `include_lines` (boolean)
- `include_tracking_link` (boolean)
- `stop_id` (integer, required): The stopId.

### `locate2u_search_stops` (~69 tokens)

Find stops by source reference

Find stops by the source reference that the integration stored on them. Locate2u API: GET /stops/search.

Input parameters:

- `include_items` (boolean)
- `include_lines` (boolean)
- `include_tracking_link` (boolean)
- `source_reference` (string, required)

### `locate2u_list_scheduled_stops` (~88 tokens)

List scheduled stops

List stops scheduled for a day (default: today in the team's zone), with paging. Locate2u API: GET /stops/scheduled.

Input parameters:

- `include_shipments` (boolean)
- `skip` (integer)
- `take` (integer)
- `team_region_id` (integer)
- `trip_date` (string): Day yyyy-mm-dd.

### `locate2u_list_unassigned_stops` (~60 tokens)

List unassigned stops

List stops that no driver has yet. Locate2u API: GET /stops/unassigned.

Input parameters:

- `include_shipments` (boolean)
- `team_region_id` (integer)
- `trip_date` (string)

### `locate2u_list_stop_notes` (~44 tokens)

List notes of a stop

List all notes on a stop, with attachments. Locate2u API: GET /stops/{id}/notes.

Input parameters:

- `stop_id` (integer, required)

### `locate2u_get_stop_pod_answers` (~55 tokens)

Get proof-of-delivery answers of a stop

Get the answers a driver gave to the proof-of-delivery questions on a stop. Locate2u API: GET /stops/{id}/podquestionanswers.

Input parameters:

- `stop_id` (integer, required)

### `locate2u_get_shipment` (~64 tokens)

Get a shipment

Get a shipment with its pickup and drop stops and items. Locate2u API: GET /shipments/{id}.

Input parameters:

- `include_cost_and_charge_lines` (boolean)
- `include_tracking_link` (boolean)
- `shipment_id` (integer, required)

### `locate2u_list_unassigned_shipments` (~64 tokens)

List unassigned shipments

List shipments that no team member has yet. Locate2u API: GET /shipments/unassigned.

Input parameters:

- `pickup_within_km_distance` (number)
- `team_region_id` (integer)
- `trip_date` (string)

### `locate2u_list_shipment_notes` (~42 tokens)

List notes of a shipment

List all notes on a shipment. Locate2u API: GET /shipments/{id}/notes.

Input parameters:

- `shipment_id` (integer, required)

### `locate2u_get_team_trips_summary` (~58 tokens)

Summarize the team's trips for a day

Summary of every trip in the team on a day: driver, distance, time, stop counts, status. Locate2u API: GET /team/trips/{tripDate}.

Input parameters:

- `trip_date` (string, required)

### `locate2u_list_team_trips` (~54 tokens)

List all trips of the team for a day

All trips (assigned and unassigned) for a day, each with its driver and stops. Locate2u API: GET /trips/team/{tripDate}.

Input parameters:

- `trip_date` (string, required)

### `locate2u_get_driver_trip` (~78 tokens)

Get a driver's trip for a day

Get the trip of one team member on a day, optionally filtered by status. Locate2u API: GET /trips/user/{publicUserId}/{tripDate}.

Input parameters:

- `include_lines` (boolean)
- `public_user_id` (string, required)
- `status` (string)
- `trip_date` (string, required)

### `locate2u_get_trip` (~49 tokens)

Get a trip by id

Get one trip by id with its stops. Locate2u API: GET /trips/id/{id}.

Input parameters:

- `include_lines` (boolean)
- `trip_id` (integer, required)

### `locate2u_list_runs` (~74 tokens)

List runs for a day

List the runs scheduled for a day, optionally for one team member, customer or run number. Locate2u API: GET /runs/{tripDate}.

Input parameters:

- `customer_id` (integer)
- `run_number` (string)
- `team_member` (string)
- `trip_date` (string, required)

### `locate2u_team_travel_statistics` (~69 tokens)

Team travel statistics

Distance and time driven by the team's members and asset groups over a date range. Locate2u API: GET /team/reports/travel-statistics.

Input parameters:

- `from_date` (string)
- `team_region_id` (integer)
- `to_date` (string)

### `locate2u_list_customer_ratings` (~95 tokens)

List delivery ratings

Delivery ratings that customers left for the team's stops over a date range. Locate2u API: GET /team/{teamId}/customer-ratings.

Input parameters:

- `end_date` (string, required)
- `higher_ratings` (boolean)
- `lower_ratings` (boolean)
- `start_date` (string, required)
- `team_id` (integer, required): The team id (from locate2u_get_team).

### `locate2u_search_items` (~87 tokens)

Search inventory items

Search inventory items by keyword, warehouse or status. Locate2u API: GET /items/search.

Input parameters:

- `item_status` (string)
- `keyword` (string)
- `location_status` (string)
- `page` (integer): Page number (starts at 1).
- `per_page` (integer): Results per page.
- `warehouse_id` (integer)

### `locate2u_get_item` (~37 tokens)

Get an inventory item

Get one inventory item by id. Locate2u API: GET /items/{id}.

Input parameters:

- `item_id` (integer, required)

### `locate2u_add_stop_note` (~76 tokens)

Add a note to a stop

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.

Input parameters:

- `note` (string, required): The note text.
- `stop_id` (integer, required)

### `locate2u_add_shipment_note` (~92 tokens)

Add a note to a shipment

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.

Input parameters:

- `note` (string, required): The note text.
- `shipment_id` (integer, required)
- `stop_id` (integer): A stop of the shipment the note belongs to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 63
- 2026-10-31: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://locate2u.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/locate2u/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-locate2u/locate2u