Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.starlordz12/inav-mcp

PYPI · INAV-MCP

MCP server for iNAV flight-controller configuration and diagnostics

Available components

+12 this week 75 Trust /100

Last scanned (10 hours ago)

Scores higher than 68% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to starlordz12/inav-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 25 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4983 tokens (~131/item across 38 items; 35 tools + 3 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (6% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_flight_mode" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 37 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 +10
    • Stability: unverified → 0.70 ▲ functional
  • 9 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/inav-mcp@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo starlordz12/inav-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/starlordz12/inav-mcp/.github/workflows/publish.yml@refs/tags/v1.0.0
Rekor log index 3500334763
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:87545eb323460cec5b7a91ce74142dafc9e54e906a8a1ff80f7072e3ce51577f

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 35 exposed · ~4,798 tokens

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 →

Tool Tokens
apply_aircraft_setup ~153

Apply the declared aircraft profile to the FC, then save and reboot. On iNAV this is an ATOMIC operation: the commands are applied in one CLI session, backed up first, then SAVED to EEPROM (the only way changes persist) and the FC reboots. We reconnect automatically and verify by read-back. If any command fails, ALL changes are rolled back (nothing is saved). Gates: - A profile must be defined via define_aircraft(). - Connected and not armed. - confirm=True required (dry-run by default). Args: confirm: True to apply+save+reboot. Default False = dry-run (shows commands).

NameTypeReqDescription
confirmboolean––

No output schema declared.

No examples provided.

assign_switch ~231

Map a multi-position switch's detents to flight modes in one call. Computes the µs range for each detent and writes one 'aux' assignment per mode. Dry-run by default. Gates: connected, not armed, auto-backup before write. Args: switch_channel: 1-based AUX number the switch is on (1 = AUX1 = RC channel 5). switch_positions: Number of detents on the switch: 2, 3, or 6. mode_per_position: Map of position → mode name. Position keys may be "low"/"mid"/"high" (for 2/3-pos) or "1".."N" / "pos1".., e.g. {"low": "ANGLE", "mid": "HORIZON", "high": "MANUAL"}. confirm: True to apply. Default False = dry-run.

NameTypeReqDescription
confirmboolean––
mode_per_positionobjectyes–
switch_channelintegeryes–
switch_positionsintegeryes–

No output schema declared.

No examples provided.

backup_config ~100

Save the current FC config to a timestamped backup file. Runs 'diff all' in the CLI and writes the output to ./backups/<timestamp>.txt. NOTE: on iNAV, leaving the CLI reboots the FC, so this reboots and then auto-reconnects (~7s). The result includes 'rebooted': True. Args: label: Optional suffix added to the filename for easy identification.

NameTypeReqDescription
label–––

No output schema declared.

No examples provided.

board_info ~57

Read flight-controller identity over MSP. Returns: FC variant (e.g. 'INAV'), firmware version, board/target name, API version, build date/time/git revision, and sensors detected. Requires an active connection (call connect first).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

calibrate_accelerometer ~118

Calibrate the accelerometer (zero-level). Fixes most 'not level' / 'accel not calibrated' arming blocks. Sends MSP_ACC_CALIBRATION; iNAV samples for ~2s and saves to EEPROM automatically (no reboot). BEFORE running: set the board/aircraft on a LEVEL surface in its normal flight orientation and DO NOT move it until this returns. Gates: connected, not armed, confirm=True (dry-run otherwise).

NameTypeReqDescription
confirmboolean––

No output schema declared.

No examples provided.

calibrate_magnetometer ~83

Calibrate the compass (magnetometer). Only useful if a compass is installed. Sends MSP_MAG_CALIBRATION; you then have ~30s to rotate the aircraft 360° around all three axes. iNAV saves the result automatically. Gates: connected, not armed, confirm=True (dry-run otherwise).

NameTypeReqDescription
confirmboolean––

No output schema declared.

No examples provided.

check_config ~74

Compare the FC's actual configuration against the declared aircraft profile. Runs 'diff all' via CLI, parses key settings, and reports mismatches against the profile declared with define_aircraft(). Also checks if ARM mode is assigned to a switch. Useful after apply_aircraft_setup() or to sanity-check a partially configured FC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_failsafe ~87

Read and explain the failsafe configuration (what happens on RC loss). Reads all `failsafe_*` settings via CLI `get failsafe`, summarises the RC-loss procedure in plain English, and flags risky setups (procedure NONE; RTH without GPS). NOTE: reads over CLI; exiting CLI reboots the FC, so this reboots and reconnects (~7s).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clear_flight_mode ~99

Remove all switch assignments for a flight mode (disables its slots via CLI 'aux'). Dry-run by default. Gates: connected, not armed, auto-backup before write. Args: mode_name: Exact mode name (e.g. "HORIZON", "NAV RTH"). confirm: True to apply. Default False = dry-run.

NameTypeReqDescription
confirmboolean––
mode_namestringyes–

No output schema declared.

No examples provided.

cli ~284

Raw CLI escape hatch — run any iNAV CLI command directly. Read-only commands (diff, get, status, dump, tasks, help, version) run and the FC reboots on CLI exit (auto-reconnected). Write commands (set, aux, feature, smix, ...) require confirm_for_writes=True and are SAVED (persist + reboot), since on iNAV exiting CLI without save discards changes. SAFETY — motor commands: a 'motor ...' command drives a LIVE motor output and can spin a propeller. It is gated separately from ordinary writes: it requires props_removed=True (NOT confirm_for_writes), refuses if the board is armed, and is NEVER saved — it's a momentary bench test that stops when the FC reboots on CLI exit. Prefer the dedicated write tools (they back up and verify). Use this for one-off commands the other tools don't cover. Args: command: The CLI command to run (without trailing newline). confirm_for_writes: Set True to allow (and persist) write commands. props_removed: Set True to allow a live 'motor' test — ONLY after physically removing all propellers from the aircraft.

NameTypeReqDescription
commandstringyes–
confirm_for_writesboolean––
props_removedboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

cli_batch ~430

Run MANY CLI commands in ONE CLI session — a single reboot for the whole batch. On iNAV, leaving the CLI ALWAYS reboots the FC, so every separate cli() call costs a full reboot + USB re-enumeration + reconnect (~7s). Doing a run of commands one cli() call at a time means one reboot PER command — the rapid reboot cadence is disruptive and can even knock the board into DFU/bootloader mode. This collapses N commands into ONE session = ONE reboot. Prefer it for any ad-hoc multi-command work (several `get` reads, or several `set` writes). (The dedicated write tools — apply_aircraft_setup, set_flight_mode, etc. — already batch internally; this is the escape hatch for everything else.) Behaviour: - All read-only batch (get/diff/dump/status/tasks/version): the session exits WITHOUT saving — no EEPROM write, nothing persists. Still one reboot (unavoidable on iNAV), but reads are free of a save. - Any write (set/aux/feature/…): requires confirm_for_writes=True; a backup is taken first and the whole batch is SAVED once at the end (persist + reboot). If ANY command is rejected by the FC, the batch exits WITHOUT saving so nothing partial persists (all-or-nothing). - Live `motor` commands and session-control verbs (save/exit/batch) are rejected up front — motor tests must never be saved (use cli(..., props_removed=True) / test_motor()), and the batch manages save/exit itself. Args: commands: Ordered list of CLI commands to run in one session. confirm_for_writes: Set True to run and persist a batch containing writes. Returns per-command output, whether it saved, the backup path (if it wrote), and the measured reboot/reconnect seconds for the single reboot.

NameTypeReqDescription
commandsarrayyes–
confirm_for_writesboolean––

No output schema declared.

No examples provided.

configure_gps ~148

Enable the GPS feature and set the receiver provider / SBAS (atomic CLI write). Args: provider: GPS provider token — e.g. UBLOX | NMEA | MSP (the FC validates it). sbas: Optional SBAS mode — AUTO | EGNOS | WAAS | MSAS | GAGAN | NONE. confirm: True to apply (save+reboot). Dry-run otherwise. Gates: connected, not armed, auto-backup. After applying, give the GPS time to acquire satellites and check read_gps().

NameTypeReqDescription
confirmboolean––
providerstring––
sbas–––

No output schema declared.

No examples provided.

connect ~106

Open the serial connection to the FC and return board identity. Args: port: Serial port, e.g. 'COM3' (Windows) or '/dev/ttyACM0' (Linux). baud: Baud rate (default 115200 — matches iNAV's USB VCP default). Returns board variant, firmware version, target name, API version, build info, and a summary of detected sensors.

NameTypeReqDescription
baudinteger––
portstringyes–

No output schema declared.

No examples provided.

define_aircraft ~340

Define the aircraft hardware profile and generate a configuration plan. This is an OFFLINE planner — no FC connection required. Call it first to review the generated CLI commands, then call apply_aircraft_setup() to apply. Args: name: A descriptive name for this aircraft (e.g., "My FPV Wing"). wing_type: One of: flying_wing, conventional, vtail, twin_tail, delta. esc_protocol: One of: DSHOT600, DSHOT300, DSHOT150, MULTISHOT, ONESHOT125, PWM. cells: LiPo battery cell count (e.g. 4 for 4S). fc_target: Optional FC board name (e.g. MATEKF405). Used for target hints. motor_kv: Optional motor KV rating (informational only). motor_poles: Motor pole count for RPM telemetry (default 14; verify with your motor). servo_count: Optional total servo count (informational). notes: Free text notes to store with the profile. Returns a plan dict with: - profile: the stored profile - commands: the CLI commands to apply - summary: human-readable description - warnings: things to verify before/after applying

NameTypeReqDescription
cellsintegeryes–
esc_protocolstringyes–
fc_target–––
motor_kv–––
motor_polesinteger––
namestringyes–
notes–––
servo_count–––
wing_typestringyes–

No output schema declared.

No examples provided.

diagnose ~71

Full diagnostic sweep — the flagship troubleshooter. Collects: arming flags, sensor health, RC channels, battery, GPS, attitude, and mode assignments. Runs all diagnostic rules and returns a prioritized problem list with concrete fixes for each issue found. Use this when 'something is wrong but I'm not sure what.'

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

disconnect ~15

Close the serial connection to the FC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_fc ~132

Auto-detect which serial port has a flight controller, so you don't guess. Briefly opens each likely USB-serial port and asks for MSP identity; returns the ports that answered as an FC (variant + firmware). Then call connect(port). Args: baud: Baud to probe at (default 115200, iNAV's USB VCP default). probe_all: If True, probe EVERY serial port; otherwise only USB-serial-looking ones (safer — avoids poking unrelated devices like Bluetooth/modems).

NameTypeReqDescription
baudinteger––
probe_allboolean––

No output schema declared.

No examples provided.

get_aircraft_profile ~28

Return the currently declared aircraft profile. Call define_aircraft() first to set a profile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_status ~52

Read FC status via both MSP and CLI. Returns MSP_STATUS data (cycle time, sensor bits, CPU load, arming flags) plus the human-readable output of the CLI 'status' and 'tasks' commands.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_backups ~55

List saved config backups under ./backups/, newest first. No FC needed. Returns each backup's path, modified time, size, line count, and label — so you can pick one to replay with restore_config(path).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_flight_modes ~112

List all available flight modes and their current switch assignments. Returns: - all_modes: every mode the FC knows about (id + name + assigned flag) - assigned_modes: which modes are on which aux channel and range - unassigned_modes: mode names with no switch assignment yet - arm_assigned: bool — critical to know before first flight Tip: call read_rc_channels() to identify which channel your switches use, then use assign_switch() to map modes to them.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_serial_ports ~73

List all available serial ports. Use this to find the COM port (Windows) or /dev/tty* (Linux/macOS) for the FC. Plug in the FC, run this, and look for a new entry (often labelled 'STM32' or 'CP210x' for iNAV boards).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

read_gps ~57

Live GPS status: fix type, satellites, position, speed, HDOP + nav-readiness. Read-only (MSP_RAW_GPS, no reboot). Use this before relying on RTH or any position-holding navigation mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_rc_channels ~61

Read live RC channel values via MSP. Returns up to 16 channel values in microseconds (988–2012 µs typical). Core UX: flip a switch and watch which channel value changes — that's the aux channel to use when assigning flight modes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_sensors ~76

Read live sensor values: attitude, per-sensor health, and analog (battery). Good for a quick sanity pass before flying: - Attitude should read ~0°/0° when the aircraft is level. - All required sensors (gyro, acc) should report OK. - Battery voltage should match your pack's cell count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_tuning ~65

Read fixed-wing PID gains, rates, and key filter cutoffs (via CLI). Returns PIDs grouped by axis, plus rate and low-pass-filter settings. NOTE: reads over CLI; exiting CLI reboots the FC, so this reboots and reconnects (~7s).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

restore_config ~128

Restore FC config by replaying a backup file's CLI commands, then save+reboot. On iNAV this is atomic: a pre-restore backup is taken, the file's commands are replayed in one CLI session, then SAVED to EEPROM and the FC reboots (we reconnect). If any line errors, all changes are rolled back. Args: path: Path to a backup file (as returned by backup_config). confirm: Must be True to apply. Dry-run by default.

NameTypeReqDescription
confirmboolean––
pathstringyes–

No output schema declared.

No examples provided.

save_and_reboot ~108

Save the running config to EEPROM and reboot the FC. Takes a backup, then 'save' (persist + reboot), then auto-reconnects (~7s). NOTE: the dedicated write tools already save automatically on iNAV, so you rarely need this — it's for persisting changes made via the raw cli() reads or to force a clean reboot. Args: confirm: Must be True to proceed. Dry-run by default.

NameTypeReqDescription
confirmboolean––

No output schema declared.

No examples provided.

set_failsafe ~304

Set the core failsafe behaviour (atomic CLI write: backup → apply → save+reboot). Only the arguments you pass are changed; dry-run by default. For other failsafe_* knobs (distances, angles) use cli('set failsafe_... = N', confirm_for_writes=True). Args: procedure: RC-loss action — one of DROP | LAND | SET-THR | RTH | NONE. The exact accepted tokens depend on firmware; an invalid value is rejected by the FC and the whole write is rolled back. throttle_us: failsafe_throttle in µs (used by SET-THR / LAND). Clamped 1000–2000. delay_s: Guard time after RC loss before failsafe triggers (failsafe_delay). iNAV stores this in 0.1 s units, so this is converted ×10. off_delay_s: Time the failsafe stage runs before the motor is killed (failsafe_off_delay), also 0.1 s units (×10). confirm: True to apply (saves + reboots). Dry-run otherwise. Gates: connected, not armed, auto-backup. RTH without GPS will not work — use DROP/LAND.

NameTypeReqDescription
confirmboolean––
delay_s–––
off_delay_s–––
procedure–––
throttle_us–––

No output schema declared.

No examples provided.

set_flight_mode ~234

Assign a flight mode to an aux channel range (read-modify-write via CLI 'aux'). Finds an existing slot for this mode+channel (to modify) or the first free slot (to create), then writes the assignment. Dry-run by default. Gates: connected, not armed, auto-backup before write. Requires confirm=True to apply. Args: mode_name: Exact mode name as shown by list_flight_modes (e.g. "ANGLE", "NAV RTH"). aux_channel: 1-based AUX number (1 = AUX1 = RC channel 5), matching list_flight_modes. range_low: Range start in µs (900–2100). range_high: Range end in µs (must be > range_low, ≤ 2100). confirm: True to apply. Default False = dry-run (returns the command only).

NameTypeReqDescription
aux_channelintegeryes–
confirmboolean––
mode_namestringyes–
range_highintegeryes–
range_lowintegeryes–

No output schema declared.

No examples provided.

set_nav ~213

Set core fixed-wing navigation / RTH parameters (atomic CLI write). Only the arguments you pass are changed. Dry-run by default. Args: rth_altitude_m: Return-to-home altitude, metres (nav_rth_altitude, stored cm). rth_climb_first: Climb to RTH altitude before heading home (nav_rth_climb_first). rth_allow_landing: NEVER | ALWAYS | FS_ONLY (nav_rth_allow_landing). loiter_radius_m: Fixed-wing loiter radius, metres (nav_fw_loiter_radius, stored cm). confirm: True to apply (save+reboot). Dry-run otherwise. Gates: connected, not armed, auto-backup. RTH needs a working GPS and a home fix.

NameTypeReqDescription
confirmboolean––
loiter_radius_m–––
rth_allow_landing–––
rth_altitude_m–––
rth_climb_first–––

No output schema declared.

No examples provided.

set_pid ~156

Set fixed-wing PID gains for ONE axis (atomic CLI write). Changes only the terms you pass. Dry-run by default. Args: axis: roll | pitch | yaw. p, i, d, ff: Gains for fw_p_<axis> / fw_i_<axis> / fw_d_<axis> / fw_ff_<axis>. confirm: True to apply (save+reboot). Dry-run otherwise. ⚠ PID changes alter flight behaviour — change gradually and test carefully. Gates: connected, not armed, auto-backup.

NameTypeReqDescription
axisstringyes–
confirmboolean––
d–––
ff–––
i–––
p–––

No output schema declared.

No examples provided.

suggest_mode_layout ~160

Recommend a fixed-wing flight-mode/switch layout. Pure knowledge — no FC needed. Suggests which switches to use for ARM, flight modes (ANGLE/HORIZON/MANUAL), and (with GPS) NAV RTH / NAV LAUNCH, with the exact aux channels and µs ranges. Args: skill_level: beginner | intermediate | advanced (tailors the advice). num_switches: How many spare switches you have available. has_gps: True if a GPS module is installed (enables RTH suggestion). Returns a layout plan you can hand to assign_switch() to apply.

NameTypeReqDescription
has_gpsboolean––
num_switchesinteger––
skill_levelstring––

No output schema declared.

No examples provided.

test_motor ~315

Spin ONE motor briefly for a bench test (direction / wiring / response). ⚠ DANGER: this drives a LIVE motor output. REMOVE ALL PROPELLERS FIRST. Safety gates (enforced in code): - props_removed=True is REQUIRED (refuses otherwise), - refuses if the FC reports armed, - confirm=True is REQUIRED (dry-run preview otherwise), - throttle clamped to 1000–2000 µs, duration clamped to 0.2–5.0 s, - the motor is ALWAYS commanded back to stop (1000 µs) when the test ends. The override is live (MSP, not saved); it also stops if the FC reboots or loses power. Args: motor: 1-based motor number (1 = motor 1). Only this motor spins; all others are held at 1000 µs (stop). throttle_us: Output in µs (1000 = stop, ~1100 = gentle, 2000 = full). Keep it LOW for a direction check. duration_s: How long to hold the output (0.2–5.0 s). props_removed: MUST be True — confirms props are physically removed. confirm: MUST be True to actually run.

NameTypeReqDescription
confirmboolean––
duration_snumber––
motorintegeryes–
props_removedboolean––
throttle_usinteger––

No output schema declared.

No examples provided.

why_wont_it_arm ~73

Decode the FC's arming-prevention flags into plain English. This is the #1 question from new iNAV users. Each set bit is mapped to: - A flag name - A plain-language reason - A concrete fix Also checks whether ARM mode is assigned to a switch.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.starlordz12/inav-mcp server?

io.github.starlordz12/inav-mcp runs locally as a PyPI package, launched with uvx inav-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · inav-mcp

# add to Claude Code
claude mcp add starlordz12-inav-mcp -- uvx inav-mcp
Common questions

What is the io.github.starlordz12/inav-mcp server?

io.github.starlordz12/inav-mcp is listed in the public MCP registry as io.github.starlordz12/inav-mcp. MCP server for iNAV flight-controller configuration and diagnostics. This page covers its PyPI package (inav-mcp).

Is the io.github.starlordz12/inav-mcp server safe to use?

io.github.starlordz12/inav-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 io.github.starlordz12/inav-mcp server expose?

io.github.starlordz12/inav-mcp exposes 35 tools: list_serial_ports, connect, disconnect, board_info, find_fc, and 30 more. Their descriptions and schemas cost roughly 4,798 tokens of context every time the server is loaded.

Is the io.github.starlordz12/inav-mcp server still maintained?

io.github.starlordz12/inav-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.starlordz12/inav-mcp server under?

io.github.starlordz12/inav-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.starlordz12/inav-mcp server?

VerifyMCP ran 15 checks on io.github.starlordz12/inav-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.starlordz12/inav-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.