Skip to content
UDSLib logo

UDSLib MCP server

Which MCP servers are UDSLib's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to UDSLib

Whose server it is
  • Registry namecom.udslib/uds-toolboxverified in the MCP registry

The registry name sits under udslib.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools7
  • Server calls itselfuds-toolbox
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 78 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • Parameters are untyped or undescribed in 3 of 7 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 10, the first on 2026-10-25
  • INITE MCP score84 of 100answers 100 · definitions 90 · context 100 · use 0 · connects 100
  • Answered100% of days10 of 10 daily checks
  • Median first answer67 ms
  • Space in an agent's context≈ 1,719 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a type: in 1 of 7
  • Parameters without a description: in 3 of 7

What an agent can do with it

  • not sure · Add ISO 14229 diagnostic services to an embedded ECU
  • not sure · Run UDS over CAN and CAN FD on Zephyr or FreeRTOS
  • not sure · Test ECU diagnostics from a host tool or test rig

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-25
  • analyze_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…

  • decode_uds

    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…

  • 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…

  • decode_isotp

    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…

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

  • 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)…

  • udslib_integration

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http udslib https://mcp.udslib.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.udslib.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.