# io.github.mrfentmen/traccar-mcp (npm · traccar-mcp)

MCP server for Traccar: devices, positions, g MCP: real tools for real work.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `traccar-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp)

## Channel facts

- Registry: `npm`
- Package: `traccar-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1648 tokens (~47/item across 35 items; 35 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_device" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.mrfentmen/traccar-mcp server?

io.github.mrfentmen/traccar-mcp runs locally as an npm package, launched with npx -y traccar-mcp. 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 mrfentmen-traccar-mcp -- npx -y traccar-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-traccar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "traccar-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-traccar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "traccar-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-traccar-mcp -- npx -y traccar-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-traccar-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "traccar-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-traccar-mcp --command npx --arg -y --arg traccar-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-traccar-mcp:
    command: "npx"
    args: ["-y", "traccar-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-traccar-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "traccar-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-traccar-mcp -t stdio -c npx -a -y traccar-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-traccar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "traccar-mcp"
      ]
    }
  }
}
```

## 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-21 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 63)

First indexed and scored.

## MCP tools (35)

### `get_server_info` (~29 tokens)

Read Traccar server identity and version. Use it to check the base URL and credentials work.

### `get_server_statistics` (~23 tokens)

Read live server statistics: connected devices, active sessions and message counters.

### `get_session` (~26 tokens)

Show the Traccar user the configured credentials belong to, including their role and limits.

### `list_devices` (~24 tokens)

List every GPS device the account can see, with status and last update time.

### `create_device` (~67 tokens)

Register a new device. Body is a Traccar device object, e.g. { "name": "Van", "uniqueId": "123456789012345" }.

Input parameters:

- `device` (object, required): Traccar device JSON (name and uniqueId are required by the server)

### `update_device` (~53 tokens)

Update an existing device. Only the fields present in the body are changed by Traccar.

Input parameters:

- `device` (object, required): Fields to change, as Traccar device JSON
- `id` (integer, required): Device id

### `delete_device` (~30 tokens)

DESTRUCTIVE: permanently delete a device and its stored positions.

Input parameters:

- `id` (integer, required): Device id

### `list_positions` (~88 tokens)

List recent GPS positions, newest first. Filter by device and an ISO 8601 time range.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string): Start of the range, ISO 8601 e.g. 2025-01-31T00:00:00Z
- `to` (string): End of the range, ISO 8601

### `list_groups` (~21 tokens)

List device groups, used to share devices and reports between users.

### `create_group` (~45 tokens)

Create a device group. Body is Traccar group JSON, e.g. { "name": "Delivery" }.

Input parameters:

- `group` (object, required): Traccar group JSON

### `update_group` (~41 tokens)

Rename or re-parent a group.

Input parameters:

- `group` (object, required): Fields to change, as Traccar group JSON
- `id` (integer, required): Group id

### `delete_group` (~33 tokens)

DESTRUCTIVE: delete a device group. Devices inside it are not deleted.

Input parameters:

- `id` (integer, required): Group id

### `list_geofences` (~26 tokens)

List geofences (drawn areas) used for enter/exit alerts.

### `create_geofence` (~60 tokens)

Create a geofence. Provide a WKT area, e.g. POLYGON ((lon lat, lon lat, ...)) in Traccar geofence JSON.

Input parameters:

- `geofence` (object, required): Traccar geofence JSON (name and area)

### `update_geofence` (~49 tokens)

Change a geofence's name, description or area.

Input parameters:

- `geofence` (object, required): Fields to change, as Traccar geofence JSON
- `id` (integer, required): Geofence id

### `delete_geofence` (~37 tokens)

DESTRUCTIVE: delete a geofence. Past events that referenced it stay in history.

Input parameters:

- `id` (integer, required): Geofence id

### `list_drivers` (~25 tokens)

List drivers, each with the unique id used to identify them on a device.

### `create_driver` (~53 tokens)

Create a driver. Body is Traccar driver JSON, e.g. { "name": "Sam", "uniqueId": "DRV-1" }.

Input parameters:

- `driver` (object, required): Traccar driver JSON

### `update_driver` (~42 tokens)

Update a driver's name or unique id.

Input parameters:

- `driver` (object, required): Fields to change, as Traccar driver JSON
- `id` (integer, required): Driver id

### `delete_driver` (~25 tokens)

DESTRUCTIVE: delete a driver.

Input parameters:

- `id` (integer, required): Driver id

### `list_maintenance` (~21 tokens)

List maintenance schedules (by odometer, hours or date).

### `create_maintenance` (~78 tokens)

Create a maintenance schedule. Body is Traccar maintenance JSON, e.g. { "name": "Oil change", "type": "totalDistance", "start": "2025-01-01T00:00:00Z", "period": 10000 }.

Input parameters:

- `maintenance` (object, required): Traccar maintenance JSON

### `update_maintenance` (~40 tokens)

Update a maintenance schedule.

Input parameters:

- `id` (integer, required): Maintenance id
- `maintenance` (object, required): Fields to change, as Traccar maintenance JSON

### `delete_maintenance` (~27 tokens)

DESTRUCTIVE: delete a maintenance schedule.

Input parameters:

- `id` (integer, required): Maintenance id

### `get_report_summary` (~87 tokens)

Totals per device for a time window: distance, average and max speed, engine hours, fuel used.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string, required): Start of the window, ISO 8601
- `groupId` (integer): Every device in this group
- `to` (string, required): End of the window, ISO 8601

### `get_report_trips` (~84 tokens)

List trips (movement segments) in a time window, with distance, duration and speeds.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string, required): Start of the window, ISO 8601
- `groupId` (integer): Every device in this group
- `to` (string, required): End of the window, ISO 8601

### `get_report_stops` (~82 tokens)

List stops in a time window, with address and how long the vehicle stayed.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string, required): Start of the window, ISO 8601
- `groupId` (integer): Every device in this group
- `to` (string, required): End of the window, ISO 8601

### `get_report_events` (~84 tokens)

List events (alarms, geofence crossings, device status changes) in a time window.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string, required): Start of the window, ISO 8601
- `groupId` (integer): Every device in this group
- `to` (string, required): End of the window, ISO 8601

### `get_report_route` (~81 tokens)

Return the full position trace for a time window, for plotting or distance checks.

Input parameters:

- `deviceId` (integer): Only this device
- `from` (string, required): Start of the window, ISO 8601
- `groupId` (integer): Every device in this group
- `to` (string, required): End of the window, ISO 8601

### `list_command_types` (~41 tokens)

List the remote commands a device supports, e.g. engineStop or positionPeriodic.

Input parameters:

- `deviceId` (integer): Limit to the commands this device supports

### `send_command` (~66 tokens)

Send a remote command to a device. Body is Traccar command JSON, e.g. { "deviceId": 3, "type": "engineStop" }. Some commands cost SMS credit.

Input parameters:

- `command` (object, required): Traccar command JSON with deviceId and type

### `list_users` (~20 tokens)

List user accounts on the server with their role and limits.

### `create_user` (~58 tokens)

Create a user account. Body is Traccar user JSON, e.g. { "name": "Sam", "email": "sam@example.com", "password": "..." }.

Input parameters:

- `user` (object, required): Traccar user JSON

### `update_user` (~50 tokens)

Update a user account: name, email, limits, expiry or administrator flag.

Input parameters:

- `id` (integer, required): User id
- `user` (object, required): Fields to change, as Traccar user JSON

### `delete_user` (~32 tokens)

DESTRUCTIVE: delete a user account. Their devices are not removed.

Input parameters:

- `id` (integer, required): User id

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 63

## Common questions

### What is the io.github.mrfentmen/traccar-mcp server?

io.github.mrfentmen/traccar-mcp is listed in the public MCP registry as io.github.mrfentmen/traccar-mcp. MCP server for Traccar: devices, positions, g MCP: real tools for real work. This page covers its npm package (traccar-mcp).

### Is the io.github.mrfentmen/traccar-mcp server safe to use?

io.github.mrfentmen/traccar-mcp scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/traccar-mcp server expose?

io.github.mrfentmen/traccar-mcp exposes 35 tools: get_server_info, get_server_statistics, get_session, list_devices, create_device, and 30 more. Their descriptions and schemas cost roughly 1,648 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/traccar-mcp server still maintained?

io.github.mrfentmen/traccar-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.mrfentmen/traccar-mcp server under?

io.github.mrfentmen/traccar-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/traccar-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/traccar-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/traccar-mcp
- Socket report: https://socket.dev/npm/package/traccar-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-traccar-mcp/traccar-mcp
