# Toyota & Lexus (pypi · toyota-mcp)

Toyota & Lexus vehicles: fuel, range, location, trips, health, climate, charging, commands

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

## Components

- pypi · `toyota-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/zepgram-toyota/toyota-mcp.md), [page](https://verifymcp.io/servers/zepgram-toyota/toyota-mcp)

## Channel facts

- Registry: `pypi`
- Package: `toyota-mcp`
- Version: `0.3.5`
- 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-09-20.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 9 of 65 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 90/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2136 tokens (~82/item across 26 items; 26 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Toyota & Lexus MCP server?

Toyota & Lexus runs locally as a PyPI package, launched with uvx toyota-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 zepgram-toyota -- uvx toyota-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "zepgram-toyota": {
      "command": "uvx",
      "args": [
        "toyota-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zepgram-toyota": {
      "command": "uvx",
      "args": [
        "toyota-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add zepgram-toyota -- uvx toyota-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zepgram-toyota": {
      "type": "local",
      "command": [
        "uvx",
        "toyota-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zepgram-toyota --command uvx --arg toyota-mcp
```

### Hermes

```yaml
mcp_servers:
  zepgram-toyota:
    command: "uvx"
    args: ["toyota-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "zepgram-toyota": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "toyota-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add zepgram-toyota -t stdio -c uvx -a toyota-mcp
```

### Other

```json
{
  "mcpServers": {
    "zepgram-toyota": {
      "command": "uvx",
      "args": [
        "toyota-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-09-20 (score 66, +1)

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

### 2026-09-18 (score 65, +1)

- [functional] Package version: 0.3.4 → 0.3.5

### 2026-09-16 (score 64, +1)

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

### 2026-09-15 (score 63, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 62, +1)

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

### 2026-09-10 (score 61, +1)

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

### 2026-09-07 (score 60, +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.

## MCP tools (26)

### `toyota_list_vehicles` (~44 tokens)

Vehicles on the account

Every vehicle on the connected account, and which one the tools act on.

Use for: which cars can I ask about? Choosing one is toyota_select_vehicle.

Output parameters:

- `note`
- `selected`: vin_suffix of the vehicle the tools act on.
- `vehicles` (array)

### `toyota_select_vehicle` (~63 tokens)

Choose the vehicle to act on

Point every other tool at one vehicle of the account, and remember it.

Use when the account holds several vehicles, or to switch between them.

Input parameters:

- `vin` (string, required): VIN of the vehicle, or the last four characters shown by toyota_list_vehicles.

Output parameters:

- `name` (string)
- `note` (string)
- `powertrain` (string)
- `vin_suffix` (string)

### `toyota_get_vehicle_info` (~77 tokens)

Vehicle identity and capabilities

Model, year, plate, colour, first-use date, connected-services subscriptions and
which remote capabilities Toyota declares for this car.

Use for: what car is this? when was it registered? is the connected
subscription still active? can it be locked remotely? Capability flags
are indicative only — see remote_capabilities.note.

Output parameters:

- `alias`
- `colour`
- `connected_services_status`
- `date_of_first_use`
- `fuel_type_code`: Raw Toyota code, e.g. 'B' for petrol.
- `image_url`
- `manufactured_on`
- `model`
- `model_year`
- `powertrain` (string)
- `registration_number`
- `remote_capabilities`
- `remote_services_status`
- `subscriptions` (array)
- `vin_suffix` (string): Last four characters of the VIN.

### `toyota_get_status` (~93 tokens)

Vehicle doors, windows and locks

Doors, windows, trunk, hood, lock state, lights and rear-seat reminder.

Use for: is the car locked? are windows or doors open? did I leave the
lights on? Lock state is
pushed by the car when parked and can lag — always cite
freshness.vehicle_reported_at when answering. Warning lights are NOT
here; use toyota_get_health for alerts and maintenance.

Output parameters:

- `all_locked` (string): 'locked' if every reporting door is locked, 'unlocked' if any reporting door is unlocked, 'unknown' if no door reported a lock state.
- `doors`
- `freshness`
- `hood` (string)
- `lights`: Hazard, tail and head lights — 'on' means left on while parked.
- `overall_status`: Toyota's aggregate verdict for the car, e.g. 'ok'.
- `rear_seat_reminder`
- `warning_count`
- `windows`

### `toyota_get_energy` (~69 tokens)

Fuel, range and battery

Remaining fuel, driving range and (when applicable) battery state.

Use for: how much range is left? how full is the tank? is it charging?
On self-charging full hybrids Toyota exposes no battery data — the
response says so explicitly in battery_note instead of returning nulls.

Output parameters:

- `battery`: Plug-in battery state; only for PHEV/EV powertrains.
- `battery_note`: Why battery data is absent, when it is.
- `freshness`
- `fuel_level_percent`: Fuel tank level, percent.
- `fuel_range`: Range on fuel alone.
- `powertrain` (string)
- `total_range`: Total remaining range reported by the car.

### `toyota_get_odometer` (~31 tokens)

Odometer reading

Total distance on the odometer.

Use for: how many kilometers/miles are on the car?

Output parameters:

- `freshness`
- `odometer`

### `toyota_get_charging` (~78 tokens)

Charging state and schedules

Plug-in battery: charge level, charging status, EV range, time to full, schedules.

Use for: is it charging? how much EV range? when is the next scheduled
charge? Plug-in hybrids and electric vehicles only — other powertrains
get an explicit "not applicable" error (use toyota_get_energy).

Output parameters:

- `battery_level_percent`
- `can_set_next_charging_event`
- `charging_status`: Raw Toyota status, e.g. 'none', 'charging'.
- `ev_range`
- `ev_range_with_ac`
- `freshness`
- `fuel_level_percent`: Plug-in hybrids only.
- `next_charging_event`: Type and time of the next scheduled charging event.
- `next_scheduled_window`: Next active schedule window (start → end), if any.
- `note` (string)
- `powertrain` (string)
- `remaining_charge_minutes`: Minutes until fully charged, when charging.
- `schedules` (array)

### `toyota_get_location` (~77 tokens)

Last parked position

Last parked position of the vehicle: coordinates, Google Maps link, address.

Use for: where is the car? The address needs the server started with
\--addresses osm or fr. The position updates only when the car
parks — while driving it shows the last parking spot; cite
freshness.vehicle_reported_at when answering.

Output parameters:

- `address`: Postal address; needs --addresses osm or fr.
- `freshness`
- `google_maps_url` (string)
- `latitude` (number)
- `longitude` (number)
- `place`: Named place from --places within 200 m, e.g. 'home'.
- `place_label`: Toyota's place name, if any.

### `toyota_get_last_trip` (~57 tokens)

Last trip details

Most recent trip: distance, duration, consumption, hybrid mode split, places.

Use for: how was the last trip? what did the last drive consume?
Start/end addresses need the server started with --addresses osm or fr.

Output parameters:

- `freshness`
- `trip`

### `toyota_get_trips` (~92 tokens)

Recent trips

Individual trips over a recent window, newest first.

Use for: list this week's trips, when did the car last drive?
For averages over a period, prefer toyota_get_trip_summary.
For windows beyond 92 days, use toyota_get_trip_summary.

Input parameters:

- `days` (integer): Calendar days to cover, ending today (inclusive).
- `limit` (integer): Maximum number of trips to return.

Output parameters:

- `freshness`
- `note`: Set when the window is empty or the list was truncated by limit.
- `retention_note` (string)
- `returned_count` (integer)
- `total_in_window` (integer): Trips recorded in the window before applying limit.
- `trips` (array): Newest first.
- `window_from` (string)
- `window_to` (string)

### `toyota_get_trip_summary` (~125 tokens)

Driving statistics over a period

Aggregated driving statistics over a rolling window or a calendar period.

Use for: average consumption over the last 7 days, EV-mode share this
month, total distance this year. Consumption is recomputed over the
whole window (total fuel vs total distance), not a mean of daily means.
Pass period to match the app's calendar figures.

Input parameters:

- `days` (integer): Calendar days to cover, ending today (inclusive).
- `period`: Calendar period as shown in the MyToyota app (today, this_week, this_month, this_year); overrides days.

Output parameters:

- `average_consumption`: Recomputed over the whole window (total fuel vs total distance).
- `average_speed`
- `countries` (array): ISO 3166-1 alpha-2 codes of countries driven in.
- `days_with_driving` (integer)
- `ev_distance`
- `ev_duration_hours`
- `ev_ratio_percent`: Share of the distance driven in electric mode.
- `ev_time_ratio_percent`: Share of the driving time spent in electric mode.
- `freshness`
- `fuel_consumed`
- `note`: Set when the window contains no trips.
- `period`: Set when the window is a calendar period (as in the app).
- `total_distance`
- `total_duration_hours` (number)
- `window_from` (string)
- `window_to` (string)

### `toyota_get_health` (~50 tokens)

Vehicle health and maintenance

Warning lights, oil indicators, recent notifications and the service history.

Use for: any alerts on the car? when was it last serviced? Toyota
exposes service history, not upcoming maintenance deadlines.

Output parameters:

- `engine_oil_indicators` (array): Raw oil-quantity indicators reported by the car; empty means nothing flagged.
- `freshness`
- `last_service`
- `notifications` (array): Latest 10, newest first.
- `service_history` (array): All recorded services, newest first.
- `service_note` (string)
- `warning_lights` (array)
- `warning_lights_caveat` (string)

### `toyota_get_climate` (~83 tokens)

Remote climate state and preset

Remote pre-conditioning state (running or stopped, temperatures) and the saved
preset a remote start would apply (target temperature, duration, defrosters,
heated seats).

Use for: is the climate running? what temperature is the preset?
Starting or stopping it is done with toyota_start_climate /
toyota_stop_climate when remote commands are enabled.

Output parameters:

- `current_temperature`
- `duration_minutes`: Programmed run time of the current session.
- `freshness`
- `is_on`
- `note` (string)
- `preset`: What a remote start would apply.
- `started_at`
- `status`: Raw Toyota state, e.g. 'stopped', 'running'.
- `target_temperature`

### `toyota_find_fuel_stations` (~119 tokens)

Cheapest fuel stations near the car

Cheapest stations selling a given fuel around the car's last parked position.

Use for: where can I fill up cheaply near the car? France only:
prices come from the French government open-data feed and need the
server started with --addresses fr.

Input parameters:

- `fuel` (string): Fuel to price: e10, sp95, sp98, e85, gazole (diesel) or gplc.
- `limit` (integer): Number of stations.
- `radius_km` (integer): Search radius in km.

Output parameters:

- `around`: The car's last parked position.
- `freshness`
- `fuel` (string)
- `note` (string)
- `radius_km` (integer)
- `stations` (array): Cheapest first.

### `toyota_refresh_data` (~76 tokens)

Refresh vehicle data

Re-fetch status, telemetry and location from Toyota's cloud.

Rarely needed — the car pushes new data only at ignition-off, so
answers refresh themselves as the car is driven. Use only when the
user just parked and wants the very latest position or status.
This reads Toyota's cloud; it never wakes the car.

Output parameters:

- `freshness`
- `note` (string)
- `refreshed` (boolean)

### `toyota_lock_doors` (~82 tokens)

Lock the doors

Lock the doors, then verify against the state the car reports.

Only when the user explicitly asked to lock the car. Call with confirm=false first when in doubt; the report says whether the car confirmed the new state.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_unlock_doors` (~84 tokens)

Unlock the doors

Unlock the doors, then verify against the state the car reports.

Security-sensitive: only when the user explicitly asked to unlock the car in this conversation, never on your own initiative. Preview with confirm=false unless the user already confirmed.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_lock_trunk` (~52 tokens)

Lock the trunk

Lock the trunk only, then verify against the state the car reports.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_unlock_trunk` (~73 tokens)

Unlock the trunk

Unlock the trunk only (doors stay locked), then verify against the state the car reports. Only on the user's explicit request; preview with confirm=false unless the user already confirmed.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_find_car` (~59 tokens)

Flash the hazard lights

Flash the hazard lights briefly so the user can spot the car — silent. Verified by the car reporting back.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_sound_horn` (~73 tokens)

Sound the horn briefly

Sound a short horn signal to locate the car — audible to everyone around it; prefer toyota_find_car unless the user asked for sound. Verified by the car reporting back.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_close_windows` (~67 tokens)

Close the windows

Close all power windows, then verify against the state the car reports. Not every model supports it; Toyota answers 'vehicle not supported' when not.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_start_climate` (~116 tokens)

Start remote climate

Start remote pre-conditioning with the saved preset (duration, defrosters, seats).

On a hybrid this runs the engine — never start it in an enclosed
space. Only when the user explicitly asked; preview with confirm=false
unless the user already confirmed. Verified against the climate state
the car reports.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.
- `temperature_celsius`: Target cabin temperature; defaults to the saved preset.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_stop_climate` (~68 tokens)

Stop remote climate

Stop remote pre-conditioning, then verify against the climate state the car reports.

Only when the user explicitly asked; preview with confirm=false when in doubt.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_charge_now` (~91 tokens)

Start charging now

Start charging the plug-in battery immediately, ahead of any schedule.

Plug-in hybrids and electric vehicles only; the car must be plugged
in. Only when the user explicitly asked; preview with confirm=false
when in doubt. Verified against the charging state the car reports.

Input parameters:

- `confirm` (boolean): true sends the command to the car; false (default) only previews what would happen and sends nothing.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

### `toyota_wake_vehicle` (~87 tokens)

Wake the car and re-read its state

Ask the car to report its current state right now, then re-read doors and climate.

The passive reads only see what the car pushed when it parked; this
sends the same wake request the MyToyota app uses. It costs the car a
little 12 V battery and cellular time — use it when the user needs the
state as of now, not routinely.

Output parameters:

- `charging`
- `climate`
- `command` (string)
- `detail` (string)
- `doors`
- `elapsed_seconds`
- `status` (string): 'needs_confirmation' = nothing was sent; 'verified' = the car reported the new state; 'accepted' = Toyota accepted the command but the car has not confirmed it yet; 'failed' = the car rejected it.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/zepgram-toyota/toyota-mcp#diagnostics

## Score history

- 2026-09-20: 66
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 78
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61
- 2026-09-10: 61
- 2026-09-09: 60
- 2026-09-08: 60
- 2026-09-07: 60
- 2026-09-06: 59
- 2026-09-05: 55
- 2026-09-04: 55
- 2026-09-03: 55
- 2026-09-02: 55
- 2026-09-01: 55
- 2026-08-31: 55
- 2026-08-30: 55
- 2026-08-29: 55

## Common questions

### What is the Toyota & Lexus MCP server?

Toyota & Lexus is an MCP server listed in the public MCP registry as io.github.zepgram/toyota. Toyota & Lexus vehicles: fuel, range, location, trips, health, climate, charging, commands. This page covers its PyPI package (toyota-mcp).

### Is the Toyota & Lexus MCP server safe to use?

Toyota & Lexus scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Toyota & Lexus MCP server expose?

Toyota & Lexus exposes 26 tools: toyota_list_vehicles, toyota_select_vehicle, toyota_get_vehicle_info, toyota_get_status, toyota_get_energy, and 21 more. Their descriptions and schemas cost roughly 1,986 tokens of context every time the server is loaded.

### Is the Toyota & Lexus MCP server still maintained?

Toyota & Lexus is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/toyota-mcp/
- Socket report: https://socket.dev/pypi/package/toyota-mcp
- Repository: https://github.com/zepgram/toyota-mcp
- Changelog RSS feed: https://verifymcp.io/servers/zepgram-toyota/toyota-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zepgram-toyota/toyota-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zepgram-toyota/toyota-mcp