# UDS Toolbox (remote · mcp.udslib.com)

Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.udslib.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp.md), [page](https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp)

## Channel facts

- Endpoint: `https://mcp.udslib.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-udslib-uds-toolbox 'https://mcp.udslib.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-udslib-uds-toolbox": {
      "url": "https://mcp.udslib.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-udslib-uds-toolbox": {
      "type": "http",
      "url": "https://mcp.udslib.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-udslib-uds-toolbox]
url = "https://mcp.udslib.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-udslib-uds-toolbox": {
      "type": "remote",
      "url": "https://mcp.udslib.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-udslib-uds-toolbox --url 'https://mcp.udslib.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-udslib-uds-toolbox:
    url: "https://mcp.udslib.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-udslib-uds-toolbox": {
      "Transport": "http",
      "Url": "https://mcp.udslib.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-udslib-uds-toolbox -t streamable-http -u 'https://mcp.udslib.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-udslib-uds-toolbox": {
      "type": "http",
      "url": "https://mcp.udslib.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-03 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 79, +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.

### 2026-10-30 (score 78, +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.

### 2026-10-28 (score 77, +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.

### 2026-10-26 (score 76, +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-10-23 (score 75, +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.

### 2026-10-21 (score 74, +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.

### 2026-10-19 (score 73, +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.

## MCP tools (7)

### `analyze_trace` (~225 tokens)

Analyze CAN trace

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.

Input parameters:

- `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.

### `decode_uds` (~132 tokens)

Decode UDS message

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.

Input parameters:

- `direction` (string): Optional hint to disambiguate.
- `hex` (string, required): PDU bytes, e.g. "7F 34 78" or "0x22 0xF1 0x90" (no ISO-TP header).

### `build_uds_request` (~425 tokens)

Build UDS request

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.

Input parameters:

- `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, required)
- `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).

### `decode_isotp` (~180 tokens)

Decode ISO-TP trace

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.

Input parameters:

- `decodeUds` (boolean): Decode each reassembled message as UDS (default true).
- `frames` (required): 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.

### `decode_dtc` (~115 tokens)

Decode DTC

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.

Input parameters:

- `dtc` (string, required): Three bytes hex ("01 23 45") or a code ("P0123-45").
- `status` (string|integer): Optional status byte, e.g. "0x09".

### `uds_reference` (~108 tokens)

UDS reference

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.

Input parameters:

- `topic` (string, required)

### `udslib_integration` (~161 tokens)

UDSLib integration plan

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.

Input parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 70
- 2026-10-13: 70
- 2026-10-12: 69
- 2026-10-11: 69
- 2026-10-10: 68
- 2026-10-07: 67
- 2026-10-06: 67
- 2026-10-04: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.udslib.com/mcp
- Repository: https://github.com/Artomatica/udslib.com
- Website: https://udslib.com/mcp.html
- Changelog RSS feed: https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-udslib-uds-toolbox/mcp