# pingpoint [Health: Active]

**Category:** 📦 Delivery  
**Repository:** https://github.com/sudzikcoin/pingpoint-freight-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 224  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pingpoint-2

## Description
Live truck GPS tracking: create loads, read live position, ETA and trip stats, cancel a load.

## Tools
Capabilities this server exposes over MCP:

- **create_load** — Creates a freight load; PingPoint texts the driver link to `driverPhone
- **get_load_position** — Live state of a load
- **get_trip_stats** — Aggregated summary of the whole GPS trip (meant for a DELIVERED load; mid-trip returns the trip so far)
- **cancel_load** — Cancels a load: status CANCELLED, tracking stops, nothing deleted, no refund (idempotent)
- **update_load_status** — Not part of the API** — statuses are GPS-verified
- **get_pricing** — Current USD price list
- **get_balance** — Prepaid balance

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pingpoint": {
    "command": "npx",
    "args": ["-y","@suverselabs/pingpoint-mcp"]
  }
}
```

## Documentation

## What pingpoint does

The pingpoint MCP server exposes PingPoint’s freight-tracking functions to MCP-compatible agents. It is designed for US trucking workflows where a broker, logistics application, or AI agent needs visibility into a truckload without relying on phone calls or a corporate telematics system.

An agent can create a load with the driver’s phone number and pickup and delivery stops. PingPoint sends the driver an SMS link for onboarding. Once the driver connects, position data can be read through the API, including current state, ETA, route progress, stop timing, distance, dwell information, and on-time status.

The service supports both phone GPS and compatible ELD dongles connected through the driver’s app. The README identifies IOSiX and Pacific Track PT30 hardware as tested devices. PingPoint also supports multi-stop loads and provides a public tracking link in the creation response.

## How it works

Load creation requires an E.164 driver phone number plus pickup and delivery arrays. Each stop needs an address, city, state, and ZIP code. The returned load number is used for later requests. A customer reference can prevent duplicate creation, and an idempotency key makes retries safe after network failures.

GPS events drive the load lifecycle. Entering and leaving geofences advances statuses such as `AT_PICKUP`, `IN_TRANSIT`, `AT_DELIVERY`, and `DELIVERED`. The final delivery status is set when the truck leaves the last delivery zone. Statuses cannot be changed manually through the API, and `update_load_status` is not an available API operation.

The live-load response includes up to 500 recent GPS points, a stop timeline, route-derived ETA data, and trip measurements. Trip statistics aggregate recorded pings and are intended for completed loads, although an in-progress trip returns the data collected so far.

## Setup and configuration

Install the MCP package with:

```bash
npm i @suverselabs/pingpoint-mcp
```

The package provides seven tools over stdio and is intended for Claude and other MCP-capable agents. Production use requires a PingPoint agent API key. The documented account flow is to sign up at PingPoint, open Integrations → Agent API, issue a key, and retrieve it by email.

A shared sandbox key is also documented for testing. Sandbox loads use simulated routes and the same geofence behavior as live loads, but they do not contact a real driver. Sandbox data is shared, rate-limited to 30 loads per hour across users of the key, and should not contain real phone numbers or addresses.

## Tools and capabilities

The pingpoint MCP server provides these tools:

- `create_load`: Creates a freight load and causes PingPoint to text the driver link to the supplied phone number.
- `get_load_position`: Reads the current load state, including live position and related tracking data.
- `get_trip_stats`: Returns an aggregate summary for the recorded GPS trip.
- `cancel_load`: Marks a load as cancelled and stops tracking without deleting it. The operation is idempotent and does not refund the load.
- `get_pricing`: Retrieves the current price list in USD.
- `get_balance`: Reads the account’s prepaid balance.
- `update_load_status`: Listed as unavailable because statuses are GPS-verified rather than manually written.

The underlying API also documents webhooks for pushing load events to an endpoint, although webhook configuration is outside the listed MCP tools.

## Limitations and notes

The pingpoint MCP server does not provide a manual status-update operation. Delivery confirmation is handled through the carrier’s workflow rather than a PingPoint vendor operation. Cancellation stops tracking but leaves the load record in place and does not issue a refund.

The live tracking process depends on the driver opening the SMS link and completing onboarding. ELD support is routed through the phone app, not directly from the dongle to the network. The sandbox is unsuitable for private operational data because its key and loads are shared. Sandbox records are removed after at least an hour, and the shared usage cap can return `429 SANDBOX_RATE_LIMITED`.

_Full upstream README: https://allmcps.com/mcp/pingpoint-2/readme_