OpenDeviceDB MCP server

by opendevicedb.org·org.opendevicedb/opendevicedb·v0.3.0·33 stars

No reviews yet

Check 21,000+ devices with open firmware or protocols before reverse engineering one.

A94/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A94/100

full report

Adoption

Growing

33 stars126 downloads/wk

Reviews

Write one

Nobody has reviewed OpenDeviceDB yet.

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

OpenDeviceDB tools (3, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

list_sources
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.
publish_findingswrite action
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
request_device
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 \u{1F44D} 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.

Public scan report

scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it

no findings

Code scan4 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 3 days ago15/15
Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How OpenDeviceDB compares

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

Safety score: 94/100; higher than 96% of 48,255 servers
Tools: 3; the typical server has 7
Tools that change things: 33%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 33; more than 92% of 28,688 servers
Downloads a week: 126; more than 68% of 12,191 servers with a package

What its tools let an agent do: 2 read · 1 send or post

Install OpenDeviceDB in Claude Code, Cursor or VS Code

Runs npx -y @opendevicedb/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add opendevicedb -- npx -y @opendevicedb/mcp

Add to Cursor

What the publisher says

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

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.

(official guide, difficulty, risks), and /detect/ finds a plugged or nearby device by its USB id or Bluetooth name, in the browser.

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

vendor cloud is still needed; the directory filters devices that work with no cloud.

Freedom: each project says what stays non-free (vendor blobs, modem, Wi-Fi…) and whether the

reverse-engineering job, claim the device, publish findings when done.

Agents: query it through the MCP server (packages/mcp) before starting a

tuya-local, OpenRGB, libgphoto2, LineageOS, postmarketOS/Nura, coreboot, rtl_433, Gadgetbridge, Klipper, Marlin, Rockbox, Valetudo, thingino, tuya-cloudcutter, QMK, SANE, OpenPrinting, libwacom, Betaflight, EdgeTX…) are aggregated by importers (packages/importers), with a link back to each source.

Existing databases (25 today: OpenWrt, Zigbee2MQTT, Z-Wave JS, Tasmota, ESPHome,

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.

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 stdio

Code: AGPL-3.0-or-later (see LICENSE). Data: CC BY-SA 4.0 (see LICENSE-DATA.md).

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

OpenDeviceDB: common questions

Is OpenDeviceDB MCP server safe?: Yes, by our scan: it is graded A (94/100). Read the OpenDeviceDB safety report
How do I install OpenDeviceDB?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does OpenDeviceDB need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is OpenDeviceDB maintained?: The last commit was 10 days ago (2026-10-25). The latest release is v0.3.0.
How does OpenDeviceDB compare with other MCP servers?: safety score 94/100 (higher than 96% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.