io.github.partymola/bosch-flow-mcp
PYPI · BOSCH-FLOW-MCP · SCANNED SEP 20
MCP server for Bosch eBike Flow (BES3): battery health, charge cycles, components, and ride data.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1847 tokens (~153/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.partymola/bosch-flow-mcp server?
io.github.partymola/bosch-flow-mcp runs locally as a PyPI package, launched with uvx bosch-flow-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 · bosch-flow-mcp
claude mcp add partymola-bosch-flow-mcp -- uvx bosch-flow-mcp
{
"mcpServers": {
"partymola-bosch-flow-mcp": {
"command": "uvx",
"args": [
"bosch-flow-mcp"
]
}
}
} {
"servers": {
"partymola-bosch-flow-mcp": {
"command": "uvx",
"args": [
"bosch-flow-mcp"
]
}
}
} codex mcp add partymola-bosch-flow-mcp -- uvx bosch-flow-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"partymola-bosch-flow-mcp": {
"type": "local",
"command": [
"uvx",
"bosch-flow-mcp"
],
"enabled": true
}
}
} openclaw mcp add partymola-bosch-flow-mcp --command uvx --arg bosch-flow-mcp
mcp_servers:
partymola-bosch-flow-mcp:
command: "uvx"
args: ["bosch-flow-mcp"] {
"McpServers": {
"partymola-bosch-flow-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"bosch-flow-mcp"
]
}
}
} assistant mcp add partymola-bosch-flow-mcp -t stdio -c uvx -a bosch-flow-mcp
{
"mcpServers": {
"partymola-bosch-flow-mcp": {
"command": "uvx",
"args": [
"bosch-flow-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
- Package version: 0.6.0 → 0.7.0 functional
- 16 Sept 26 −2
- Stability: pass → 0.87 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed pypi/bosch-flow-mcp@0.7.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
bosch_battery_trends ~208
Analyse battery health trends for your Bosch eBike over time. Computes per-period averages and deltas for: - Charge cycle count (total, rate of accumulation) - Average battery level at time of sync - Lifetime energy delivered (total kWh ever pushed through the battery) - Remaining energy trend (indicates capacity degradation over time) A declining remaining_energy_wh at a constant charge level indicates the battery capacity is degrading. Compare early and recent snapshots for a long-term health picture. Args: bike_id: Optional bike UUID. If omitted, includes all bikes. period: Aggregation period. Options: "weekly", "monthly" (default), "quarterly". start_date: Start date (YYYY-MM-DD, YYYY-MM, Nd, or None for all data). end_date: End date. Default: today.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| end_date | – | – | – |
| period | string | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_activities ~204
List e-bike rides with per-ride summary metrics. Live read from the Bosch rider-activity API (no cache). Each ride includes distance, elevation gain/loss, avg/max speed, cadence, measured rider power, calories, rider-vs-motor energy share, assist-mode distance split (metres per mode), CO2 (emissions / car-equivalent / saved), and ABS/brake events. Heart rate is not recorded by the bike (it has no HR sensor) - pair with a wrist device for HR. Args: start_date: Window start (YYYY-MM-DD, YYYY-MM, or "30d"). Default 30 days ago. end_date: Window end. Default today. bike_id: Optional bike UUID filter. limit: Optional cap on rides returned (most recent first).
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| end_date | – | – | – |
| limit | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_activity_detail ~112
Get the per-point track for one ride (GPS + speed/elevation/cadence/power). Live read. Returns a downsampled track (~500 points per ride): per-point cumulative distance (m), speed (km/h), elevation (m), cadence, rider power (W), and GPS lat/lon. Get the activity_id from bosch_get_activities. Args: activity_id: The ride UUID from bosch_get_activities.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_batteries ~189
Get battery state and health for your Bosch eBike. Returns charge level, remaining energy, total capacity, charge cycles (total / on-bike / off-bike), lifetime energy delivered, and software version. Each sync captures a snapshot, building a time series of battery health. Use latest_only=False with a date range to see history. Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd like "30d"). Default: 30 days ago. end_date: End date. Default: today. latest_only: If True (default), return only the most recent snapshot per bike. Set to False to return all snapshots in the date range.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| end_date | – | – | – |
| latest_only | boolean | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_bike ~69
Get detailed profile for a single Bosch eBike. Returns full bike details including brand, model, frame number, and the cached raw API response which may include component info. Args: bike_id: The bike UUID from bosch_get_bikes.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_bikes ~71
List all Bosch eBikes registered to your Flow account. Returns bike names, brand, and frame numbers. Uses local cache (auto-syncs if stale). Run bosch_sync first if the list is empty. Returns a list of bikes with id, name, brand_name, and frame_number.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_capacity ~116
Get battery capacity tester diagnostic results. Shows battery health data from Bosch's official capacity tester tool, typically done at dealer service appointments. Includes remaining capacity percentage vs. original specification. Capacity-tester data comes only from the EU Data Act API; with a standard Bosch eBike Flow sign-in this is empty and the result explains why. Args: part_number: Optional battery part number to filter results. serial_number: Optional battery serial number to filter results.
| Name | Type | Req | Description |
|---|---|---|---|
| part_number | – | – | – |
| serial_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_components ~220
List registered components for your Bosch eBike with software versions. Shows the bike's components - drive unit, battery, ConnectModule, head unit, remote control, ABS - with part numbers, serial numbers, and firmware versions. The source depends on your sign-in: a standard Bosch eBike Flow account reads them from the bike profile (mobile app API); an EU Data Act (euda) client reads them from the Data Act registrations endpoint. Useful for tracking firmware versions and identifying components for warranty or service purposes. Args: bike_id: Optional bike UUID to filter to one bike. component_type: Optional component type filter, e.g. "driveUnit", "battery", "headUnit", "connectedModule", "remoteControl". Matched against the types your bikes registered, ignoring case, so every stored spelling of a type answers together. A value none of them match is refused, naming the types that are held.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| component_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_service_records ~145
Get the digital service book history for your Bosch eBike. Returns all service records logged by Bosch dealers and service centres, including dates and descriptions of work performed. Service records come only from the EU Data Act API; with a standard Bosch eBike Flow sign-in this is empty and the result explains why (register a euda client). Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd). Default: all records. end_date: End date. Default: today.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_soc ~111
Get live state-of-charge from the Bosch ConnectModule. Returns real-time battery percentage, charging status, remaining energy, and reachable range per assist mode (eco/tour/sport/turbo). Requires a ConnectModule on the bike. Data is only available when the bike is powered on, charging, or recently active. Note: This calls the Bosch mobile API live - no caching. Args: bike_id: The bike UUID from bosch_get_bikes.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_get_software_updates ~146
Get software update installation history for your Bosch eBike. Returns all firmware/software update reports, showing which components were updated, from which version to which version, and when. This history comes only from the EU Data Act API; with a standard Bosch eBike Flow sign-in it is empty (current firmware is still available via components). Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd). Default: all records. end_date: End date. Default: today.
| Name | Type | Req | Description |
|---|---|---|---|
| bike_id | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bosch_sync ~256
Sync Bosch eBike data to the local cache. Fetches data from Bosch and stores it in SQLite. The source depends on your sign-in: a standard Bosch eBike Flow account uses the mobile app API; an EU Data Act (euda) client uses the Data Act API. Run this to populate the cache before using other bosch_get_* tools, or to refresh after a ride or charge cycle. Bikes are identified automatically from your Bosch Flow account. Battery snapshots build a time series for health trend analysis. Service records, software-update history and capacity-tester data are only available with a euda (EU Data Act) client; with a standard sign-in they report status "unavailable" rather than an empty result. Args: data_types: What to sync. Options: "all", "bikes", "batteries", "components", "service", "software_updates", "capacity". Comma-separated for multiple, e.g. "bikes,batteries". Default: "all". Returns a per-type summary: status (ok/empty/unavailable/error), record count, and a message explaining any non-ok result.
| Name | Type | Req | Description |
|---|---|---|---|
| data_types | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.partymola/bosch-flow-mcp server?
io.github.partymola/bosch-flow-mcp is listed in the public MCP registry as io.github.partymola/bosch-flow-mcp. MCP server for Bosch eBike Flow (BES3): battery health, charge cycles, components, and ride data. This page covers its PyPI package (bosch-flow-mcp).
Is the io.github.partymola/bosch-flow-mcp server safe to use?
io.github.partymola/bosch-flow-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.partymola/bosch-flow-mcp server expose?
io.github.partymola/bosch-flow-mcp exposes 12 tools: bosch_get_activities, bosch_get_activity_detail, bosch_sync, bosch_battery_trends, bosch_get_batteries, and 7 more. Their descriptions and schemas cost roughly 1,847 tokens of context every time the server is loaded.
Is the io.github.partymola/bosch-flow-mcp server still maintained?
io.github.partymola/bosch-flow-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.