MCP.Market

Usb Rea MCP server

by emirmrkaljevic·io.github.emirmrkaljevic/usb-rea·v0.7.9·1 stars

Reverse engineer USB gadgets: capture traffic, infer the protocol, generate a pyusb driver.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Usb Rea yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Usb Rea tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Usb Rea compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 12 versions in the registry since 2026-10-16, latest 2026-11-03, typically one every 1 day.

Install Usb Rea in Claude Code, Cursor or VS Code

claude mcp add usb-rea -- uvx usb-rea
Add to Cursor

What the publisher says

From the Usb Rea repository's README, as published. We do not edit it. Read it on GitHub

usb-rea — Reverse Engineer any USB gadget

<!-- mcp-name: io.github.emirmrkaljevic/usb-rea -->

Got a USB device that only ships a Windows vendor app (case LCD, RGB controller, mouse, "smart" lamp)? Click around in the vendor app while usb-rea captures the USB traffic (usbmon on Linux, USBPcap on Windows), diffs the packets per action, infers the protocol, and writes an open-source Python/libusb driver — with every conclusion linked to the exact packets that prove it.

Status: alpha (v0.2.1, on PyPI). Validated on synthetic devices, on protocols documented by liquidctl and rivalcfg, and on public Wireshark captures — see docs/VALIDATION.md. Not yet tested on a physical gadget: your captures are welcome.

Try it in 10 seconds (no hardware needed)

pip install usb-rea
usb-rea demo --device fan
fan    100%  0x5a | counter (+1 per message) | 0x10 | u16be round(value * 1 + 0) | 0x00 | u16le crc16_modbus(bytes[0:6])
color  100%  0x5a | counter (+1 per message) | 0x20 | round(value * 1 + 0) | round(value[1] * 1 + 0) | round(value[2] * 1 + 0) | u16le crc16_modbus(bytes[0:6])
mode   100%  0x5a | counter (+1 per message) | 0x30 | lookup 1→0x11, 2→0x22, 3→0x47 | 0x00 | 0x00 | u16le crc16_modbus(bytes[0:6])

It writes a synthetic capture of a fan controller, recovers the protocol, and writes report.md (every claim linked to Wireshark frame numbers) and a working pyusb driver that encodes values it never saw.

--device lamp (default) is a simple 8-bit device; --device dial shows 32-bit values and packed bitfields:

position     100%  0xa5 | 0x01 | u32le round(value * 1 + 0) | sum8(bytes[0:6])
level        100%  0xa5 | 0x02 | bits[0:4] = round(value * 1 + 0) | 0x00 | sum8(bytes[0:4])

What it can infer

Linear fits must survive leave-one-out cross-checks; otherwise usb-rea falls back to an honest lookup table and says so.

Real device workflow (Linux)

sudo modprobe usbmon
usb-rea capture start -o lamp.pcapng
usb-rea mark -m lamp.pcapng.actions.json "brightness 0%"    # then click it in the vendor app
usb-rea mark -m lamp.pcapng.actions.json "brightness 50%"   # ...repeat for 3+ values per setting
usb-rea capture stop
usb-rea report lamp.pcapng -o report.md
usb-rea scaffold lamp.pcapng -o lamp_driver.py
usb-rea dissector lamp.pcapng -o lamp.lua      # Wireshark dissector for the same protocol

Captured on Windows with USBPcap/Wireshark and no markers? Click each action with a short pause in between, then just list them in order — usb-rea splits the traffic at the pauses:

usb-rea report lamp.pcapng --labels "brightness 0%; brightness 50%; brightness 100%; power off; power on"
usb-rea scaffold lamp.pcapng --labels labels.txt -o lamp_driver.py   # one label per line

(Markers, if you have them, are a JSON list of {"label", "start", "end"} epoch timestamps.)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Usb Rea: common questions

Is Usb Rea MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Usb Rea safety report
How do I install Usb Rea?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Usb Rea need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Usb Rea maintained?
The last commit was 19 days ago (2026-10-16). The latest release is v0.7.9.
What can I use instead of Usb Rea?
Servers from other publishers that do the same job: Keploy MCP server.
How does Usb Rea compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

Alternatives to Usb Rea

Same job from other publishers: the closest match first, then the best rated.

  • Keploy
    End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
    A

More from emirmrkaljevic →