com.fpv-db/fpv-db · v1.0.0 · data-and-databases
FPV-DB is healthy: it completed an MCP handshake in 564 ms and exposes 5 tools.
Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff
Endpoint: https://fpv-db.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 564 ms |
| Last checked (UTC) | 2026-10-29T06:50:22.353Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-29T06:50:22.353Z | Healthy | 564 |
fw_param | One CLI setting of a firmware release: type, allowed range or values, firmware default (with no board config), the source line (settings.c or settings.yaml), and its history across releases (renames, range and default changes). Old names are followed through sourced renames. |
fw_diff | What changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings. |
fw_check_cli | Checks a pasted `diff all` / `dump` against a release: every `set` line whose setting does not exist, was renamed or removed, or whose value is out of range or not in the value list, plus lines that only repeat the firmware default. The release of the paste is read from its `# Betaflight / ... X.Y.Z |
part_specs | The full spec sheet of one part by its slug (the last segment of its fpv-db.com URL, e.g. iflight-xing2-2207 for /motors/iflight-xing2-2207/): specs, bench thrust table where measured, VTX table where published, the sources the specs were verified against, and caveats. |
search_parts | Finds published parts of one type by spec. `filters` maps a spec field to a number (equals, or any element of a list), a string (case-insensitive substring) or {min, max} (numeric range). `query` matches brand and model. An unknown field returns the type's field list. Example: type=motor, filters={" |