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.turbyho/fw-context-mcp

PYPI · FW-CONTEXT-MCP

Build-aware code intelligence for embedded C/C++ firmware — libclang, FTS5, call graphs, 37 tools

Available components

+3 this week 59 Trust /100

Last scanned (16 hours ago)

Scores higher than 53% of PyPI servers

Category Code Search and Documentation

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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 51 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT AND Apache-2.0 WITH LLVM-exception).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 55163 tokens (~1379/item across 40 items; 37 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (59% 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; "reset_index" implies "delete" 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 39 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 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.97 ▲ functional
    • Package version: 0.37.0 → 0.37.1 functional
  • 19 Nov 26 +1

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

  • 18 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.97 → unverified ▼ functional
  • 17 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 16 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 15 Nov 26 +1

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

  • 14 Nov 26 +3
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.20 ▲ functional
    • Package version: 0.36.0 → 0.37.0 functional
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/fw-context-mcp@0.37.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

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

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

Dependencies 51 packages
Packages resolved 51
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 37 exposed · ~50,984 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
trace_data_flow ~1,238

Trace how C/C++ data of a given type flows to a target function via libclang call paths. libclang-powered: finds functions by type signature and maps call paths through the full call graph, which text-based search cannot trace across translation units. Finds definitions whose signature mentions *type_name* (substring match, any symbol kind, most-called first), then looks for call paths from those to *to_symbol*. Returns a data flow map — useful for understanding how a data structure travels through the system to its destination. Works best for synchronous driver stacks (e.g. sensor read → I2C write). Cannot follow async flows (message queues, interrupts, RS485 callbacks). For exact call-graph queries use the ``find_*`` family; verify specific paths with ``find_call_path``. Read-only. No side effects. Requires the reference index (``fw-context index`` — refs on by default). Args: type_name: Type name to trace. E.g. ``'SensorData'`` or ``'Config::SensorData'``. to_symbol: Target symbol name. E.g. ``'uart_send'`` or ``'UART_DRIVER::send'``. project_root: Project root. Auto-detected if omitted. project: Project name or project_id — call list_projects to get them. Use it to ask about a project that is not the project of the current directory. It is an alternative to project_root, which takes a root path. Give one of the two, not both. max_depth: Maximum call path depth (default 8, max 20). limit: Maximum source functions to trace (default 15, max 15). offset: Skip this many source functions. Reads the next page; the page notice names the offset to use. timeout_ms: Maximum total execution time in milliseconds (default 30000). Clamped to 1000–300000. The budget is for one page. variant: Variant of the build (a board, or a PlatformIO environment). On a project of more than one build, give the arguments of one build as the refusal lists them: the…

NameTypeReqDescription
image––Image of the build: a separate program, such as the application or the bootloader. On a project of more than one build, give it when that build has an image name, as the refusal lists it.
limitinteger–Maximum source functions to trace (default 15, max 15).
max_depthinteger–Maximum call path depth (default 8, max 20).
offsetinteger–Skip this many source functions. Reads the next page.
project––Project name or project_id — call list_projects to get them. Use it to ask about a project that is not the project of the current directory. It is an alternative to project_root, which takes a root p…
project_root––Project root. Auto-detected if omitted. This field also accepts a project name or a project_id, but project is the clear field for those.
timeout_msinteger–Maximum total execution time in milliseconds (default 30000).
to_symbolstringyesTarget symbol name. E.g. 'uart_send' or 'UART_DRIVER::send'.
type_namestringyesType name to trace. E.g. 'SensorData' or 'Config::SensorData'.
variant––Variant of the build (a board, or a PlatformIO environment). On a project of more than one build, give the arguments of one build as the refusal lists them: the variant, the image, or the two. fw-con…
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the io.github.turbyho/fw-context-mcp server?

io.github.turbyho/fw-context-mcp runs locally as a PyPI package, launched with uvx fw-context-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 · fw-context-mcp

# add to Claude Code
claude mcp add turbyho-fw-context-mcp -- uvx fw-context-mcp
Common questions

What is the io.github.turbyho/fw-context-mcp server?

io.github.turbyho/fw-context-mcp is listed in the public MCP registry as io.github.turbyho/fw-context-mcp. Build-aware code intelligence for embedded C/C++ firmware, libclang, FTS5, call graphs, 37 tools. This page covers its PyPI package (fw-context-mcp).

Is the io.github.turbyho/fw-context-mcp server safe to use?

io.github.turbyho/fw-context-mcp scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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.turbyho/fw-context-mcp server expose?

io.github.turbyho/fw-context-mcp exposes 37 tools: check_dependencies, check_ollama, configure_llm, get_build_info, get_project_info, and 32 more. Their descriptions and schemas cost roughly 50,984 tokens of context every time the server is loaded.

Is the io.github.turbyho/fw-context-mcp server still maintained?

io.github.turbyho/fw-context-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.turbyho/fw-context-mcp server under?

io.github.turbyho/fw-context-mcp declares the MIT AND Apache-2.0 WITH LLVM-exception 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.turbyho/fw-context-mcp server?

VerifyMCP ran 15 checks on io.github.turbyho/fw-context-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.turbyho/fw-context-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.