Log inSubmit server
Pingpoint logo

Pingpoint

Track US freight loads with live GPS position, ETA, trip stats, pricing, balance, creation, and cancellation tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pingpoint

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pingpoint-2": {
      "command": "npx",
      "args": [
        "-y",
        "@suverselabs/pingpoint-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @suverselabs/pingpoint-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 13d ago.

Overview

The pingpoint MCP server connects AI agents to PingPoint’s freight-tracking API for US trucking. It creates loads, sends a driver an SMS link, and exposes live position, ETA, stop timeline, trip statistics, pricing, and prepaid balance data through MCP tools. Reach for it when an agent needs machine-readable shipment visibility without manually calling a driver. Load statuses are produced by GPS geofences, while cancellation stops tracking without deleting the load.

Use cases

  • Create freight loads from an AI logistics workflow
  • Read a truck’s live GPS position and ETA
  • Review completed-trip statistics
  • Cancel loads and stop tracking
  • Check PingPoint pricing and prepaid balance

Key features

  • Freight load creation with driver SMS onboarding
  • Live GPS position and ETA retrieval
  • Geofence-derived load statuses
  • Trip statistics and stop timelines
  • Idempotent load cancellation
  • Pricing and prepaid balance lookup

Tools7

What Pingpoint lets your agent do. Expand a tool for its parameters.

Self-reported~116 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

10/10 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @suverselabs/pingpoint-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads224Package downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed7Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Pingpoint works

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:

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

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pingpoint

pingpoint is an MCP server that connects AI agents to PingPoint’s freight-tracking API for US trucking. Its main tools create and cancel loads, read live load position, retrieve trip statistics, check current pricing, and read prepaid balance; status updates are GPS-controlled rather than manually written.

Install it with `npm i @suverselabs/pingpoint-mcp`. The package runs over stdio and is intended for Claude and other MCP-capable agents. You also need a PingPoint agent API key, obtained through the PingPoint account’s Integrations → Agent API section.

PingPoint texts the driver an onboarding link after load creation. The driver connects through the link, and the service receives background phone GPS data; supported ELD dongles can also send vehicle data through the app. Agents then read the resulting position and load state through MCP.

No. PingPoint does not provide a working manual status-update operation because statuses are verified by GPS geofences. Pickup, transit, delivery, and delivered states advance from recorded vehicle movement rather than an agent or user keyboard action.

Yes. A documented shared sandbox key creates simulated loads that follow real routes through PingPoint’s geofence engine. It does not send SMS messages or use a real driver, and sandbox loads are shared, temporary, and limited to 30 creations per hour across all users of the key.

Related MCP servers

All in Delivery All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPingpoint AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pingpoint-2?style=directory)](https://allmcps.com/mcp/pingpoint-2)
HTML Embed
<a href="https://allmcps.com/mcp/pingpoint-2"><img src="https://allmcps.com/api/badge/pingpoint-2?style=directory" alt="Pingpoint on AllMCPs" /></a>