USB LIN Converter
PYPI · UCAN-LIN-MCP
Sniff and reverse-engineer a car's LIN bus: capture, changing bits, speed detect, LDF decode
Available components
Last scanned (8 hours ago)
Scores higher than 56% of PyPI servers
Category IoT and Hardware
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 Security43
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (setup.py) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 2 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 879 tokens (~97/item across 9 items; 9 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_frame" implies "send" 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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +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.
- 3 Nov 26 +5
- Stability: unverified → 0.37 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 47
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/ucan-lin-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
| setup_py | unreviewed | <setup.py, unreviewed> |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
decode_frame ~52
Decode raw frame bytes into signal values with the loaded LDF. id like "0x0C", data hex like "05 1e".
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
detect_bus ~43
Try every speed and checksum combination and report which one sees valid frames. Use when monitor_bus shows nothing on a live bus.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds_per_try | number | – | – |
No output schema declared.
No examples provided.
device_info ~29
Converter port, firmware version, whether transmitting is allowed, and the loaded LDF (if any).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
encode_frame ~53
Build frame bytes from signal values with the loaded LDF. Signals not given keep their LDF default. Returns id and data ready for send_frame.
| Name | Type | Req | Description |
|---|---|---|---|
| frame | string | yes | – |
| signals | object | yes | – |
No output schema declared.
No examples provided.
load_ldf ~55
Load a LIN Description File so captures show signal names and values. Returns its frames and signals. Pass path "mock" with a --mock server to load the simulated bus's LDF.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
monitor_bus ~176
Listen to the bus passively and summarize what is on it. Per frame id: count, period, last data, how many distinct values were seen and changing_bits (a per-byte mask of bits that changed). 'changes' lists every data change in time order, so asking the user to press a button during the capture shows which id and bit it drives. speed: 19200 (most cars), 10417 or 9600. checksum: 'enhanced' (LIN 2.x) or 'classic' (LIN 1.x); frames with the other checksum are dropped by the converter. ids: optional filter, e.g. ["0x0C"].
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | – | – |
| duration_s | number | – | – |
| ids | – | – | – |
| speed | integer | – | – |
No output schema declared.
No examples provided.
run_master ~124
Act as the LIN master for duration_s: run a schedule that sends the `transmit` frames ([{"id": "0x0B", "data": "05"}]) and polls the `receive` ids ([{"id": "0x0C", "length": 2}]), then summarize the slave responses. Use only with the real master disconnected. Needs --allow-transmit.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | – | – |
| duration_s | number | – | – |
| receive | – | – | – |
| speed | integer | – | – |
| transmit | – | – | – |
No output schema declared.
No examples provided.
run_slave ~125
Simulate a slave node for duration_s: answer the master's headers for the `respond` ids with fixed data ([{"id": "0x0C", "data": "01 1e"}]) and capture the `listen` ids the master sends ([{"id": "0x0B", "length": 1}]). Use only with the real slave disconnected. Needs --allow-transmit.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | – | – |
| duration_s | number | – | – |
| listen | – | – | – |
| respond | – | – | – |
| speed | integer | – | – |
No output schema declared.
No examples provided.
send_frame ~106
Inject a complete frame (header + data) on the bus from monitor mode, `repeat` times about 20 ms apart, and capture the bus for a moment after. Needs --allow-transmit. The converter echoes only the header of its own frame back, so check the effect in the following traffic.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | – | – |
| data | string | yes | – |
| id | string | yes | – |
| repeat | integer | – | – |
| speed | integer | – | – |
No output schema declared.
No examples provided.
How do I install the USB LIN Converter MCP server?
USB LIN Converter runs locally as a PyPI package, launched with uvx ucan-lin-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ucan-lin-mcp
claude mcp add lukasz-juranek-lin-usb-converter -- uvx ucan-lin-mcp
What is the USB LIN Converter MCP server?
USB LIN Converter is an MCP server listed in the public MCP registry as io.github.Lukasz-Juranek/lin-usb-converter. Sniff and reverse-engineer a car's LIN bus: capture, changing bits, speed detect, LDF decode. This page covers its PyPI package (ucan-lin-mcp).
Is the USB LIN Converter MCP server safe to use?
USB LIN Converter scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 USB LIN Converter MCP server expose?
USB LIN Converter exposes 9 tools: device_info, monitor_bus, detect_bus, load_ldf, decode_frame, and 4 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Is the USB LIN Converter MCP server still maintained?
USB LIN Converter is still listed as active in the MCP registry. We last reached this channel on 5 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 USB LIN Converter MCP server under?
USB LIN Converter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.