io.github.zepgram/toyota

Toyota & Lexus

Is the Toyota & Lexus MCP server down? Yes. It has given no valid answer since 2026-10-18: crashed on start.

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

crashed on start down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-08

MCP error -32000: Connection closed
TOYOTA_USERNAME: Value error, must be the MyToyota account email address
TOYOTA_BRAND: Input should be 'T' or 'L'
TOYOTA_USE

Run it: uvx toyota-mcp@0.3.5 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/zepgram/toyota-mcp
Website: https://github.com/zepgram/toyota-mcp
Registry: active, updated 2026-09-17 · registry entry

Compare this server with others.

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

Local GPU Imagegen io.github.zc4578980-tech/local-gpu-imagegen · alive
io.github.zcsabbagh/knowledge-graph-mcp · crashed on start
Webhook.site MCP Server io.github.zebbern/webhook-mcp-server · alive
gonzalgo io.github.zengineco/gonzalgo · needs args
ZERO MCP io.github.zero-intel/zero · alive
SMLIGHT ZeroStack RF Diagnostics io.github.zerostack-rf/zerostack-mcp · alive
Personal Brain io.github.zhang-liz/personal-brain · alive
MedXpert 图书馆连接器（通用版） io.github.zhaoxinghua09-cell/medxpert-library-connector · alive

Servers that mention lexus.

io.github.pcas-io/plexus · needs your URL
Turbo Quant Memory io.github.Lexus2016/turbo-quant-memory · alive
Impact Plexus com.impactplexus/funders · alive
Japan Places — Japan Data Foundry io.github.lexusdev7/japan-foundry · alive
RegBase Japan Corporate Registry Diff io.github.lexusdev7/jp-corp-diff · alive

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

No valid answer since 2026-10-18, in every probe since then.
The process exited on start before it answered initialize. The error output is above.