UDS Toolbox
REMOTE · MCP.UDSLIB.COM
Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware.
Available components
Last scanned (4 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1411 tokens (~176/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://mcp.udslib.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=udslib.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fa4338bef2d4485e1363d91df399d713 |
| SANs: udslib.com, mcp.udslib.com, *.mcp.udslib.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.udslib.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| udslib.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.udslib.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.udslib.com/mcp | Inconclusive | 405 |
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 →
analyze_trace Analyze CAN trace ~225
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 sessions and security access, reconstructs RequestDownload/TransferData into an image with CRC32, extracts identification DIDs, and returns a root-cause finding with the frames that show it. Shows an interactive timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | An uploaded trace file: text formats above, or binary BLF, pcap, pcapng, MF4. |
| format | string | – | Default auto-detect. |
| trace | string | – | Trace text (candump, ASC, TRC or CSV). Use this or file. |
No output schema declared.
No examples provided.
build_uds_request Build UDS request ~425
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| address | string | – | request_download: e.g. "0x08000000". |
| addressBytes | integer | – | Default 4. |
| commType | – | – | comm_control communicationType, default 01. |
| control | – | – | comm_control control type. |
| counter | integer | – | transfer_data block sequence counter. |
| data | string | – | Hex payload (write_did, transfer_data, routine option record). |
| dfi | integer | – | dataFormatIdentifier, default 0. |
| did | string | – | – |
| dids | array | – | read_did: e.g. ["F190","F18C"]. |
| group | string | – | clear_dtc group, default FFFFFF. |
| hex | string | – | raw: bytes to pass through. |
| key | string | – | security_key: key bytes in hex. |
| level | integer | – | security_seed/security_key: odd seed-request level; the key is sent with level+1. |
| mask | – | – | read_dtc status mask, default FF. |
| on | boolean | – | control_dtc: true = DTC setting on. |
| rid | string | – | routine: e.g. "FF00". |
| service | string | yes | – |
| size | string | – | request_download: e.g. "0x10000". |
| sizeBytes | integer | – | Default 4. |
| subfunction | – | – | read_dtc sub-function (e.g. 2 = reportDTCByStatusMask). |
| suppress | boolean | – | tester_present: set suppressPosRspMsgIndicationBit. |
| type | – | – | session/ecu_reset sub-function (number, hex string or name). |
No output schema declared.
No examples provided.
decode_dtc Decode DTC ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dtc | string | yes | Three bytes hex ("01 23 45") or a code ("P0123-45"). |
| status | string|integer | – | Optional status byte, e.g. "0x09". |
No output schema declared.
No examples provided.
decode_isotp Decode ISO-TP trace ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decodeUds | boolean | – | Decode each reassembled message as UDS (default true). |
| 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 | – | true: warn on unpadded short frames; false: warn when padding bytes appear. |
No output schema declared.
No examples provided.
decode_uds Decode UDS message ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Optional hint to disambiguate. |
| hex | string | yes | PDU bytes, e.g. "7F 34 78" or "0x22 0xF1 0x90" (no ISO-TP header). |
No output schema declared.
No examples provided.
uds_reference UDS reference ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
No output schema declared.
No examples provided.
udslib_integration UDSLib integration plan ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| features | array | – | dtc, dtc_persist, security, authentication, bootloader, flash_tool, custom_service, periodic, roe |
| role | string | – | – |
| rtos | string | – | – |
| target | string | – | MCU or board, e.g. "STM32F103", "H563". |
| transport | string | – | – |
No output schema declared.
No examples provided.
How do I install the UDS Toolbox MCP server?
UDS Toolbox is a hosted endpoint at https://mcp.udslib.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.udslib.com
claude mcp add --transport http com-udslib-uds-toolbox 'https://mcp.udslib.com/mcp'
What is the UDS Toolbox MCP server?
UDS Toolbox is an MCP server listed in the public MCP registry as com.udslib/uds-toolbox. Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware. This page covers its hosted endpoint (https://mcp.udslib.com/mcp).
Is the UDS Toolbox MCP server safe to use?
UDS Toolbox scores 80 out of 100 on VerifyMCP. 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 UDS Toolbox MCP server expose?
UDS Toolbox exposes 7 tools: analyze_trace, decode_uds, build_uds_request, decode_isotp, decode_dtc, and 2 more. Their descriptions and schemas cost roughly 1,346 tokens of context every time the server is loaded.
Does the UDS Toolbox MCP server require authentication?
No. We connected to UDS Toolbox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UDS Toolbox MCP server still maintained?
UDS Toolbox 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.