Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
UDS Toolbox is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http uds-toolbox-mcp https://mcp.udslib.com/mcp
# 2 — ask your agent for something these tools do
# analyze_trace, decode_uds, build_uds_request and 4 more
UDS Toolbox costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http uds-toolbox-mcp https://mcp.udslib.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Analyze a whole CAN trace of a UDS diagnostic or flash session and say what went wrong. Accepts candump logs, Vector ASC, PEAK TRC (1.x/2.x), SavvyCAN or python-can CSV pasted as text, and those plus Vector BLF, Wireshark pcap/pcapng (SocketCAN) and ASAM MF4 bus logging uploaded as a file. Reassembles ISO-TP, pairs requests with responses (including 0x78 responsePending), measures P2/P2*, follows
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trace | string | no | Trace text (candump, ASC, TRC or CSV). Use this or file. |
| file | object | no | An uploaded trace file: text formats above, or binary BLF, pcap, pcapng, MF4. |
| format | string | no | Default auto-detect. |
Decode a UDS (ISO 14229-1) PDU from hex: request, positive or negative response. Names the service, sub-function (and suppressPosRsp bit), DID/RID/address fields, and for negative responses the NRC with meaning and typical cause. Unknown SIDs and NRCs are labelled, not rejected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hex | string | yes | PDU bytes, e.g. "7F 34 78" or "0x22 0xF1 0x90" (no ISO-TP header). |
| direction | string | no | Optional hint to disambiguate. |
Build a UDS request as hex with an annotated breakdown. Services: session, ecu_reset, read_did, write_did, security_seed, security_key, tester_present, routine, request_download, transfer_data, transfer_exit, clear_dtc, read_dtc, control_dtc, comm_control, raw. Numeric strings are hex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| type | no | session/ecu_reset sub-function (number, hex string or name). | |
| dids | array | no | read_did: e.g. ["F190","F18C"]. |
| did | string | no | — |
| data | string | no | Hex payload (write_did, transfer_data, routine option record). |
| level | integer | no | security_seed/security_key: odd seed-request level; the key is sent with level+1. |
| key | string | no | security_key: key bytes in hex. |
| suppress | boolean | no | tester_present: set suppressPosRspMsgIndicationBit. |
| action | string | no | — |
| rid | string | no | routine: e.g. "FF00". |
| address | string | no | request_download: e.g. "0x08000000". |
| size | string | no | request_download: e.g. "0x10000". |
| addressBytes | integer | no | Default 4. |
| sizeBytes | integer | no | Default 4. |
| dfi | integer | no | dataFormatIdentifier, default 0. |
| counter | integer | no | transfer_data block sequence counter. |
| group | string | no | clear_dtc group, default FFFFFF. |
| subfunction | no | read_dtc sub-function (e.g. 2 = reportDTCByStatusMask). | |
| mask | no | read_dtc status mask, default FF. | |
| on | boolean | no | control_dtc: true = DTC setting on. |
Reassemble ISO-TP (ISO 15765-2) messages from CAN frames, per CAN id, and decode each as UDS. Reports frame types (SF/FF/CF/FC), flow-control BS/STmin, sequence-number errors, interrupted messages, padding, and N_Bs/N_Cr/STmin timing warnings when timestamps (ms) are given. Accepts a frame list or a candump text dump.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| frames | yes | Array of {id, data, t?} (id hex string or number, data hex string or byte array, t in ms), or a candump-style multiline string. | |
| padding | boolean | no | true: warn on unpadded short frames; false: warn when padding bytes appear. |
| decodeUds | boolean | no | Decode each reassembled message as UDS (default true). |
Convert a 3-byte UDS DTC to the SAE J2012 style code (P/C/B/U + digits) plus failure type byte, or the reverse ("U0073-00" to hex). With a status byte, explains each of the 8 DTC status bits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dtc | string | yes | Three bytes hex ("01 23 45") or a code ("P0123-45"). |
| status | string/integer | no | Optional status byte, e.g. "0x09". |
Short UDS reference with ISO 14229-1 clause pointers (paraphrased). Topics: a service ID (0x27) or name, an NRC (0x78 or "nrc 78"), a DID (F190) or RID (FF00), timing (p2, p2*, s3), sessions, security (0x27 vs 0x29), reprogramming_sequence. Unknown topics return a topic list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
Plan how to integrate the UDSLib C stack (ISO 14229 UDS server/client for embedded ECUs): which repo files to take, Kconfig/config hints, an init skeleton, the closest example, and the license terms (free noncommercial / commercial). UDSLib speaks ISO-TP over CAN/CAN-FD; DoIP is not supported.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | MCU or board, e.g. "STM32F103", "H563". |
| rtos | string | no | — |
| transport | string | no | — |
| features | array | no | dtc, dtc_persist, security, authentication, bootloader, flash_tool, custom_service, periodic, roe |
| role | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install UDS Toolbox or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish UDS Toolbox can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.