FPV-DB
REMOTE · FPV-DB.COM
Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff
Available components
Last scanned (21 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 738 tokens (~147/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://fpv-db.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fpv-db.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 47bd4f3a298b0f300e86dde867699da1 |
| SANs: fpv-db.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fpv-db.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fpv-db.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fpv-db.com/mcp | Verified | 200 | |
| http (plaintext) | http://fpv-db.com/mcp | HTTPS enforced | 301 | https://fpv-db.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fw_check_cli Check a Betaflight or INAV diff ~175
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` or `# INAV/<target> X.Y.Z` header, which also picks the firmware when none is given. Other commands (aux, serial, resource) are counted, not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| firmware | string | – | Firmware (fw_check_cli: default is the one the paste's header names) |
| text | string | yes | The CLI text, up to 100 KB |
| version | string | – | Release to check against (default: latest) |
No output schema declared.
No examples provided.
fw_diff Betaflight / INAV settings diff ~93
What changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings.
| Name | Type | Req | Description |
|---|---|---|---|
| firmware | string | – | Firmware (fw_check_cli: default is the one the paste's header names) |
| from | string | yes | Older release, e.g. 4.5 |
| to | string | – | Newer release (default: latest) |
No output schema declared.
No examples provided.
fw_param Betaflight / INAV CLI setting ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| firmware | string | – | Firmware (fw_check_cli: default is the one the paste's header names) |
| name | string | yes | Setting name, as in `set <name> = ...` |
| version | string | – | Release, e.g. 2026.6.2 or 4.5 (default: latest) |
No output schema declared.
No examples provided.
part_specs FPV part spec sheet ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| type | string | – | Part type, if known |
No output schema declared.
No examples provided.
search_parts Search FPV parts ~135
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={"stator": "2207", "weight_g": {"max": 33}}.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | – |
| limit | integer | – | – |
| query | string | – | Words that must appear in brand + model |
| type | string | yes | – |
No output schema declared.
No examples provided.
How do I install the FPV-DB MCP server?
FPV-DB is a hosted endpoint at https://fpv-db.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fpv-db.com
claude mcp add --transport http com-fpv-db-fpv-db 'https://fpv-db.com/mcp'
What is the FPV-DB MCP server?
FPV-DB is an MCP server listed in the public MCP registry as com.fpv-db/fpv-db. Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff. This page covers its hosted endpoint (https://fpv-db.com/mcp).
Is the FPV-DB MCP server safe to use?
FPV-DB scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FPV-DB MCP server expose?
FPV-DB exposes 5 tools: fw_param, fw_diff, fw_check_cli, part_specs, search_parts. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Does the FPV-DB MCP server require authentication?
No. We connected to FPV-DB without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FPV-DB MCP server still maintained?
FPV-DB is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.