opendevicedb
OfficialThis MCP server lets humans and AI agents query and contribute to OpenDeviceDB, an open directory of reverse-engineered devices, firmware, protocols, and install routes.
Look up a device before reverse engineering it, using names or identifiers like FCC ID, USB VID:PID, BLE name, or Zigbee model, to check for existing protocols, open firmware, install routes, and live claims.
Search the device directory with ranked full-text search, optionally filtered by status or category, and get device IDs for deeper lookup.
Claim a device with scope, contact, and expiry to avoid duplicate work; this can create a stub record and prepares a pull-request workflow.
Publish or merge findings such as summary, status, interfaces, projects, install routes, identifiers, aliases, verification runs, and provenance, with schema validation and PR commands.
Request a device read-only by returning an existing request or a prefilled GitHub issue link; the server never posts anything.
List aggregated source databases with URLs, licenses, snapshot dates, record counts, and curated record counts to judge coverage and freshness.
Aggregates ESPHome device definitions and firmware information into OpenDeviceDB, allowing agents to query existing reverse-engineered device knowledge and publish findings.
Aggregates LineageOS device support data into OpenDeviceDB, enabling agents to look up reverse-engineered device details and contribute new findings.
Aggregates OpenWrt device database records into OpenDeviceDB, providing queryable reverse-engineering information for supported routers and devices.
Aggregates Tasmota device templates and firmware data into OpenDeviceDB, allowing agents to query existing device knowledge and publish updates.
Aggregates Zigbee2MQTT device support data into OpenDeviceDB, enabling agents to query reverse-engineered Zigbee device information and avoid duplicate work.
OpenDeviceDB
English | 简体中文
An open directory of devices whose protocols or firmware have been reverse engineered, so that nobody — human or AI agent — redoes work that already exists.
Humans: browse the directory, device pages and news on the website (
site/).Install routes and detection: device pages list how to install the open firmware (official guide, difficulty, risks), and /detect/ finds a plugged or nearby device by its USB id or Bluetooth name, in the browser.
Freedom: each project says what stays non-free (vendor blobs, modem, Wi-Fi…) and whether the vendor cloud is still needed; the directory filters devices that work with no cloud.
Agents: query it through the MCP server (
packages/mcp) before starting a reverse-engineering job, claim the device, publish findings when done.Existing databases (42 today, 32,110 devices: OpenWrt, Zigbee2MQTT, Z-Wave JS, Tasmota, ESPHome, tuya-local, OpenRGB, libgphoto2, LineageOS, postmarketOS/Nura, coreboot, rtl_433, Gadgetbridge, Klipper, Marlin, Rockbox, Valetudo, thingino, tuya-cloudcutter, QMK, SANE, OpenPrinting, libwacom, Betaflight, EdgeTX, and for cameras CHDK, Magic Lantern, OpenMemories, pktriggercord, Fujihack, plus AsteroidOS watches, Network UPS Tools, sigrok measurement instruments, GP2040-CE controllers, libratbag mice, OpenTabletDriver tablets and OpenRazer peripherals, Meshtastic radios, Armbian computers, CircuitPython boards, Ubuntu Touch and Droidian mobile Linux references…) are aggregated by importers (
packages/importers), with a link back to each source.
If it is useful to you, a ⭐ helps people with the same devices find it.
Contributions don't have to be complete: a single verified fact about a protocol (a BLE characteristic, a checksum, UART pins) helps the next person or agent go faster. See Contribute.
See SPEC.md for the design and POLICY.md for what we accept.
The first composable application pilot
adds a component/application catalogue at /components/, a real WASM processing
example, isolated web components and composition customization. Components are
independent of device records. The English OKF specification
describes the broader roadmap, including desktop export and spatial capture ports.
An experimental fwupd declaration index preserves plugin identifiers and their source context for future device mapping. It is separate from the device catalogue.
Community research, outreach history and outgoing messages are tracked in the outreach journal.
npm install
npm run validate # check every record against schema/device.schema.json
npm run import -- all # refresh data/imported/ snapshots
npm run dev # website on localhost
npm run mcp # MCP server on stdioCode: AGPL-3.0-or-later (see LICENSE). Data: CC BY-SA 4.0 (see LICENSE-DATA.md).
Available Tools
6 toolsclaim_deviceClaim a device you are about to reverse engineerA
Record that you (your human) are working on a device, with a scope, contact and expiry (default 30 days, max 90), so other agents do not duplicate the work. Creates a stub record if the device is unknown (then give vendor, model, category). Writes data/devices/.yaml in the local repository checkout (needs ODB_REPO); you then open a pull request — the result gives the exact commands.
Inputs: who (required), scope (required), contact (required), id, +6 more.
list_sourcesList the databases OpenDeviceDB aggregatesARead-only
Imported source databases with name, url, license, snapshot date and record count, plus the number of curated records. Use it to judge coverage and freshness: a device absent here may still be covered by a source that was not imported.
Inputs: no named parameters.
lookup_deviceLook up a device before reverse engineering itARead-only
CALL THIS FIRST, before you start reverse engineering any device (drone, camera, router, plug, robot, wearable...). It tells you whether the protocol or a free firmware already exists, whether someone is working on it right now (live claims), and gives a one-line recommendation (e.g. "open firmware exists: use X", "claimed by Y until Z: contact them"). Give identifiers when you have them (FCC id, USB vid:pid, BLE name, Zigbee model): they match better than names. The record's install routes (when present) say how to put the open firmware on the device: official guide, installer, difficulty, safety flags. If it answers found: false, nothing is known: call claim_device before starting.
Inputs: id, usb, model, fcc_id, +3 more.
publish_findingsPublish what you foundA
CALL THIS WHEN YOU FINISH (or stop) a reverse-engineering job, even with partial results. Merges your findings into the record: summary and status replace (status only moves forward), interfaces merge by transport+name (yours replace), projects by url, install routes by method+guide, identifiers and aliases are unioned, verification is appended. The result is validated against the schema; nothing is written on error. Link to your protocol docs/code hosted elsewhere; never include firmware images, vendor code, keys, or anything defeating Remote ID, geofencing or other safety functions (POLICY.md). Set provenance.ai_assisted honestly. Then open a pull request — the result gives the commands.
Inputs: id (required), patch (required), allow_downgrade, release_claim_of.
request_deviceRequest a device (say your user wants it)ARead-only
Use when your user wants a device to become usable with open code but will not reverse engineer it themselves (lookup_device found nothing usable). Returns the existing request to add a 👍 to, or a pre-filled link to a new public GitHub issue that the user reviews and submits. Read-only: this tool never posts anything.
Inputs: model (required), vendor (required), usb, goal, +3 more.
search_devicesSearch the device directoryARead-only
Ranked full-text search over vendor, model, aliases and identifiers across curated records and imported databases (OpenWrt, Zigbee2MQTT, Tasmota...). Use it to explore ("all DJI drones", "open-firmware cameras") or when lookup_device finds nothing and you suspect another name. Each result has an id to pass to lookup_device.
Inputs: query (required), limit, status, category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have clearly distinct roles tied to the reverse-engineering workflow: lookup, search, claim, publish, request, and list sources. lookup_device and search_devices overlap somewhat since both find devices, but the descriptions provide a clear ordering heuristic (lookup first, search when lookup fails or for exploration).
All tool names follow a consistent snake_case verb_noun pattern: publish_findings, lookup_device, search_devices, claim_device, request_device, list_sources. No mixing of camelCase or inconsistent verb styles.
Six tools is well-scoped for a device reverse-engineering coordination server. Each tool supports a distinct step in the workflow, and none appears redundant or trivial.
The surface covers the core lifecycle: discover, claim, publish findings, request additions, and inspect sources. Minor gaps exist around claim lifecycle management, such as releasing or updating an existing claim, but agents can likely work around these via existing tools and pull requests.
Maintenance
Related MCP Connectors
Open-source mods for the devices you own, with owner reports on what works.
Open-source mods for the devices you own, with owner reports on what works.
Router default logins, compliance index, MAC/OUI lookup. Reads free; submit_correction is Pro.
Repairability and durability data for EU devices from the official EPREL register
Related MCP Servers
- AlicenseAqualityBmaintenanceMAC-address (OUI) vendor lookup and router default-login directory for AI agents, backed by ssid.ai. Identify a device manufacturer from its MAC address, detect randomized/private addresses instead of reporting unknown, or fetch a router's default login IP and admin credentials — every field cited to the manufacturer's own documentation485 npm2MIT
- AlicenseAqualityBmaintenanceReverse engineer Windows-only USB gadgets: capture vendor-app traffic, infer the protocol with frame-level evidence, and generate an open Python/pyusb driver. Replay needs human confirmation.10148MIT
- AlicenseAqualityBmaintenanceEnables a local assistant to inspect your own smart-home devices by capturing and analyzing network traffic, revealing who they talk to, encryption status, open ports, and an A-F grade.6672 PyPI7MIT
- AlicenseNot gradedqualityBmaintenanceReverse engineer and port software and games from any coding agent: identify engines and builds, read Godot packs, Unity IL2CPP, .NET and native binaries (decompiling through Ghidra, IDA or Hopper), and port between Godot, Unity, Unreal and three.js with parity checks. Runs locally, only for software you own or may legally analyse.753 npm25MIT