GPS Insight MCP by usefulapi

Read vehicles, positions, idle time, fault codes, driving scores and alerts in GPS Insight.

Should I use this

Quality & Safety

A
Description quality
97%
Schema completeness
79%
Naming quality
79%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'gpsinsight_vehicle_fuel_card_transactions' name length outside 3-30 rangein gpsinsight_vehicle_fuel_card_transactions

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~2,120Tokens (tool definitions)
~866 BTypical response size
Moderate attention impact (1.66% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "gps-insight": {
      "url": "https://gps-insight.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://gps-insight.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (15)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢gpsinsight_list_vehicles(details)

List the vehicles on the account with their ids, VINs and labels. Use details=1 for all columns, or a comma list such as make,model,odometer. Good first call to find a vehicle. GET /v2/vehicle/list.

Input Schema

{
  "type": "object",
  "properties": {
    "details": {
      "description": "1 for all columns, or a comma list of columns (for example make,model,odometer).",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_read_vehicle(vehicle)

Read the record of one vehicle: id, VIN, label and serial number. GET /v2/vehicle/read.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    }
  },
  "required": [
    "vehicle"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_location(vehicle)

Get the latest position of one vehicle: address, landmark, speed, heading, ignition, odometer, driver and inputs. GET /v2/vehicle/location.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    }
  },
  "required": [
    "vehicle"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_history(vehicle, start, end)

Get the recorded positions of one vehicle between two times, with speed, ignition and odometer. GET /v2/vehicle/history.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    },
    "start": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4} \\d{1,2}:\\d{2}(:\\d{2})?$",
      "description": "Time as m/d/yyyy hh:mm:ss, for example 8/1/2015 07:15:00."
    },
    "end": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4} \\d{1,2}:\\d{2}(:\\d{2})?$",
      "description": "Time as m/d/yyyy hh:mm:ss, for example 8/1/2015 07:15:00."
    }
  },
  "required": [
    "vehicle",
    "start",
    "end"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_idle_detail(vehicle, date)

List the idle periods of one vehicle on one day, with place, duration and fuel used while idling. GET /v2/vehicle/idledetail.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4}$",
      "description": "Day as m/d/yyyy, for example 8/1/2015."
    }
  },
  "required": [
    "vehicle",
    "date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_dtc(vehicle, date)

List the diagnostic trouble codes (DTC) one vehicle reported on one day, with counts and times. GET /v2/vehicle/dtc.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4}$",
      "description": "Day as m/d/yyyy, for example 8/1/2015."
    }
  },
  "required": [
    "vehicle",
    "date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_scorecard(vehicle, timeframe)

Get the driving score of one vehicle for a period, with daily scores and the events behind them. GET /v2/vehicle/scorecard.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    },
    "timeframe": {
      "description": "Scoring period, for example week.",
      "type": "string"
    }
  },
  "required": [
    "vehicle"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_vehicle_fuel_card_transactions(vehicle, start_date, end_date)

List the fuel card transactions of one vehicle between two days. GET /v2/vehicle/fuelCardTransactions.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "type": "string",
      "minLength": 1,
      "description": "Vehicle: GPS Insight id, VIN, device serial number, label, or a unique part of the label."
    },
    "start_date": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4}$",
      "description": "Day as m/d/yyyy, for example 8/1/2015."
    },
    "end_date": {
      "type": "string",
      "pattern": "^\\d{1,2}\\/\\d{1,2}\\/\\d{4}$",
      "description": "Day as m/d/yyyy, for example 8/1/2015."
    }
  },
  "required": [
    "vehicle",
    "start_date",
    "end_date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_list_vehicle_groups

List the vehicle groups with their ids and vehicle counts. GET /v2/vehiclegroup/list.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_list_drivers

List the drivers on the account with their ids and contact fields. GET /v2/driver/list.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_list_users

List the portal users on the account with their usernames and names. GET /v2/user/list.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_list_landmarks(group)

List the landmarks (named places with a radius or polygon), optionally one landmark group. GET /v2/landmark/list.

Input Schema

{
  "type": "object",
  "properties": {
    "group": {
      "description": "Landmark group name, for example Dispatch Centers.",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_list_alerts

List the alert types configured on the account and whether each one is active. GET /v2/alert/list.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_alert_history(vehicle, alert, alert_minutes_age)

List alert events, for one vehicle or one alert id, from the last alert_minutes_age minutes. GET /v2/alert/history.

Input Schema

{
  "type": "object",
  "properties": {
    "vehicle": {
      "description": "Vehicle filter (same forms as the other vehicle tools).",
      "type": "string"
    },
    "alert": {
      "description": "Alert id, as shown in the alert history.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "alert_minutes_age": {
      "description": "Look back this many minutes.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢gpsinsight_reverse_geocode(latitude, longitude)

Turn a latitude and longitude into a street address and city. GET /v2/geocode/reverse.

Input Schema

{
  "type": "object",
  "properties": {
    "latitude": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude in decimal degrees."
    }
  },
  "required": [
    "latitude",
    "longitude"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded15 tools