FPV-DB
com.fpv-db/fpv-dbfpv-db.comstreamable-httpv1.0.0Scanned
Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
fw_check_cliChecks 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 lis…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
fw_paramOne 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
part_specsThe full spec sheet of one part by its slug (the last segment of its fpv-db.com URL, e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
fw_diffWhat changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings.No findings
Why it is in this group
- The name "fw_diff" says "diff": a word for reading.
Description, as the server wrote it What changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_partsFinds published parts of one type by spec.No findings
Why it is in this group
- The name "search_parts" says "search": a word for reading.
Description, as the server wrote it 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}}.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fpv-db https://fpv-db.com/mcpclaude mcp add --transport http fpv-db https://fpv-db.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fpv-db__fw_diff",
"mcp__fpv-db__search_parts"
],
"ask": [
"mcp__fpv-db__fw_param",
"mcp__fpv-db__fw_check_cli",
"mcp__fpv-db__part_specs"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fpv-db. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.fpv-db/fpv-db/verify?hash=afd34657057d3426c84699fbac979561b8910f1227238a091ee445f507b7d84c" | jq -e '.changed == false'Pinned hash afd34657057d, from Oct 29, 2026, 07:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.fpv-db/fpv-db/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.fpv-db/fpv-db)Source: MCP Registry. Synced Oct 29, 2026, 07:17 UTC.