Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mrfentmen/traccar-mcp

NPM · TRACCAR-MCP

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

Available components

+4 this week 69 Trust /100

Last scanned (19 hours ago)

Scores higher than 39% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1648 tokens (~47/item across 35 items; 35 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/traccar-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 35 exposed · ~1,648 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_device ~67

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

NameTypeReqDescription
deviceobjectyesTraccar device JSON (name and uniqueId are required by the server)

No output schema declared.

No examples provided.

create_driver ~53

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

NameTypeReqDescription
driverobjectyesTraccar driver JSON

No output schema declared.

No examples provided.

create_geofence ~60

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

NameTypeReqDescription
geofenceobjectyesTraccar geofence JSON (name and area)

No output schema declared.

No examples provided.

create_group ~45

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

NameTypeReqDescription
groupobjectyesTraccar group JSON

No output schema declared.

No examples provided.

create_maintenance ~78

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

NameTypeReqDescription
maintenanceobjectyesTraccar maintenance JSON

No output schema declared.

No examples provided.

create_user ~58

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

NameTypeReqDescription
userobjectyesTraccar user JSON

No output schema declared.

No examples provided.

delete_device ~30

DESTRUCTIVE: permanently delete a device and its stored positions.

NameTypeReqDescription
idintegeryesDevice id

No output schema declared.

No examples provided.

delete_driver ~25

DESTRUCTIVE: delete a driver.

NameTypeReqDescription
idintegeryesDriver id

No output schema declared.

No examples provided.

delete_geofence ~37

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

NameTypeReqDescription
idintegeryesGeofence id

No output schema declared.

No examples provided.

delete_group ~33

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

NameTypeReqDescription
idintegeryesGroup id

No output schema declared.

No examples provided.

delete_maintenance ~27

DESTRUCTIVE: delete a maintenance schedule.

NameTypeReqDescription
idintegeryesMaintenance id

No output schema declared.

No examples provided.

delete_user ~32

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

NameTypeReqDescription
idintegeryesUser id

No output schema declared.

No examples provided.

get_report_events ~84

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstringyesStart of the window, ISO 8601
groupIdinteger–Every device in this group
tostringyesEnd of the window, ISO 8601

No output schema declared.

No examples provided.

get_report_route ~81

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstringyesStart of the window, ISO 8601
groupIdinteger–Every device in this group
tostringyesEnd of the window, ISO 8601

No output schema declared.

No examples provided.

get_report_stops ~82

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstringyesStart of the window, ISO 8601
groupIdinteger–Every device in this group
tostringyesEnd of the window, ISO 8601

No output schema declared.

No examples provided.

get_report_summary ~87

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstringyesStart of the window, ISO 8601
groupIdinteger–Every device in this group
tostringyesEnd of the window, ISO 8601

No output schema declared.

No examples provided.

get_report_trips ~84

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstringyesStart of the window, ISO 8601
groupIdinteger–Every device in this group
tostringyesEnd of the window, ISO 8601

No output schema declared.

No examples provided.

get_server_info ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_server_statistics ~23

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_session ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_command_types ~41

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

NameTypeReqDescription
deviceIdinteger–Limit to the commands this device supports

No output schema declared.

No examples provided.

list_devices ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_drivers ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_geofences ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_groups ~21

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_maintenance ~21

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_positions ~88

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

NameTypeReqDescription
deviceIdinteger–Only this device
fromstring–Start of the range, ISO 8601 e.g. 2025-01-31T00:00:00Z
tostring–End of the range, ISO 8601

No output schema declared.

No examples provided.

list_users ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

send_command ~66

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

NameTypeReqDescription
commandobjectyesTraccar command JSON with deviceId and type

No output schema declared.

No examples provided.

update_device ~53

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

NameTypeReqDescription
deviceobjectyesFields to change, as Traccar device JSON
idintegeryesDevice id

No output schema declared.

No examples provided.

update_driver ~42

Update a driver's name or unique id.

NameTypeReqDescription
driverobjectyesFields to change, as Traccar driver JSON
idintegeryesDriver id

No output schema declared.

No examples provided.

update_geofence ~49

Change a geofence's name, description or area.

NameTypeReqDescription
geofenceobjectyesFields to change, as Traccar geofence JSON
idintegeryesGeofence id

No output schema declared.

No examples provided.

update_group ~41

Rename or re-parent a group.

NameTypeReqDescription
groupobjectyesFields to change, as Traccar group JSON
idintegeryesGroup id

No output schema declared.

No examples provided.

update_maintenance ~40

Update a maintenance schedule.

NameTypeReqDescription
idintegeryesMaintenance id
maintenanceobjectyesFields to change, as Traccar maintenance JSON

No output schema declared.

No examples provided.

update_user ~50

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

NameTypeReqDescription
idintegeryesUser id
userobjectyesFields to change, as Traccar user JSON

No output schema declared.

No examples provided.

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.

npm · traccar-mcp

# add to Claude Code
claude mcp add mrfentmen-traccar-mcp -- npx -y traccar-mcp
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.