Skip to content
FPV DB logo

FPV DB MCP server

Which MCP servers are FPV DB'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-29

← Back to FPV DB

Whose server it is
  • Registry namecom.fpv-db/fpv-dbverified in the MCP registry

The registry name sits under fpv-db.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-29
  • Stateanswerschecked 2026-10-29
  • Tools5
  • Server calls itselffpv-db
  • Server version1.0.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "verify a Betaflight or INAV diff against the target firmware release", the likely first call is fw_check_cli.
  • Parameters are untyped or undescribed in 2 of 5 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: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer104 ms
  • Space in an agent's context≈ 894 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 5

What an agent can do with it

  • not sure · check thrust-to-weight ratio of a planned build
  • can do · verify a Betaflight or INAV diff against the target firmware release

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 offers5 tools · read 2026-10-29
  • 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…

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

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

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

How to connect

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

{
  "mcpServers": {
    "fpv-db": {
      "type": "http",
      "url": "https://fpv-db.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http fpv-db https://fpv-db.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://fpv-db.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.