BLEA
PYPI · BLEA
Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.
Available components
Last scanned (2 hours ago)
Scores higher than 92% of PyPI servers
Category IoT and Hardware
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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 44 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Nitmi/blea). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1607 tokens (~66/item across 24 items; 24 tools + 0 resources), lean.Pass
- 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 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; "ble_unpair" 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 24 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.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 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.
- 30 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.77 functional
- 29 Sept 26 −17
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Schema quality: 1457 → 1607 ▼ functional
- Destructive annotations: pass → 0 functional
- Package version: 0.6.5 → 0.7.0 functional
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 17 Oct 2026 · Analysed pypi/blea@0.7.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 | Nitmi/blea |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Nitmi/blea/.github/workflows/release.yml@refs/tags/v0.7.0 |
| Rekor log index | 2999124298 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:34d98409cc47a54aaf1a7ac8d36e546dcf15a833e501582d04f8a13a37fe9e2e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 44 packages
| Packages resolved | 44 |
|---|---|
| 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 →
ble_capture ~131
Save a validated read-only BLE evidence package as .blea.jsonl. Capture performs one discovery and one connection, then records advertisements, GATT, bounded reads, and bounded notifications. It never writes, pairs, or changes device configuration. The output path is replaced atomically only after the final summary validates.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| max_reads | integer | – | – |
| observe_duration | number | – | – |
| output | string | yes | – |
| read_offset | integer | – | – |
| redact_identifiers | boolean | – | – |
| service_uuid | – | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_diff ~116
Compare two validated BLEA evidence files without accessing Bluetooth hardware. Transient capture metadata and notification timestamps are ignored. RSSI uses a 5 dBm tolerance by default; strict_rssi compares exact values. Device identifiers must match unless allow_different_devices is explicitly enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | – |
| allow_different_devices | boolean | – | – |
| before | string | yes | – |
| fail_on_change | boolean | – | – |
| rssi_tolerance | number | – | – |
| strict_rssi | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_doctor ~30
Check whether the local Bluetooth adapter and OS BLE backend are usable.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_exchange ~108
Subscribe first, perform one guarded write, then collect resulting notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_write | boolean | – | – |
| base64_value | – | – | – |
| confirm_device | – | – | – |
| device | string | yes | – |
| duration | number | – | – |
| hex_value | – | – | – |
| notify_characteristic | string | yes | – |
| read_back | boolean | – | – |
| response | boolean | – | – |
| text_value | – | – | – |
| timeout | number | – | – |
| write_characteristic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_inspect ~40
Discover GATT; timeout applies separately to scan, connect, and GATT operations.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_observe ~90
Observe notify/indicate characteristics on one connection for a bounded duration. When characteristics is omitted, all discovered notify/indicate characteristics are selected. Per-characteristic subscription failures remain in subscriptions while other subscriptions continue. The tool always reports cleanup evidence and never writes or pairs.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristics | – | – | – |
| device | string | yes | – |
| duration | number | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_pair ~87
Pair an exact id:<identifier> with guards; optional six-digit PIN is Windows-only. PINs are excluded from result evidence. The MCP host may retain tool arguments in its history.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_pairing | boolean | – | – |
| confirm_device | – | – | – |
| device | string | yes | – |
| pin | – | – | – |
| scan_timeout | number | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_probe ~120
Read one GATT page; inspect read_page and follow next_read_offset until null. ok=true means the page ran, not that every characteristic read succeeded. timeout applies separately to scan, connect, profile discovery, and each read. The full profile is omitted by default to keep repeated pages compact; use ble_inspect first or set include_profile=true.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| include_profile | boolean | – | – |
| max_reads | integer | – | – |
| read_offset | integer | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_read ~46
Read a characteristic; timeout applies separately to scan, connect, and GATT operations.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristic | string | yes | – |
| device | string | yes | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_replay ~154
Replay scan/inspect/probe/read/subscribe/observe/run from evidence without BLE hardware. speed=0 returns matching notifications immediately. Positive speed values preserve recorded notification gaps at the requested multiplier. Replay is always read-only and never exposes a write or exchange operation.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristic | – | – | – |
| characteristics | – | – | – |
| device | – | – | – |
| duration | number | – | – |
| evidence | string | yes | – |
| include_profile | boolean | – | – |
| max_reads | integer | – | – |
| name_contains | – | – | – |
| operation | string | yes | – |
| read_offset | integer | – | – |
| service_uuid | – | – | – |
| speed | number | – | – |
| timeout | number | – | – |
| workflow | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_scan ~37
Scan nearby BLE advertisements and return stable structured evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| name_contains | – | – | – |
| service_uuid | – | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_close ~25
Disconnect and forget an open BLE session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_close_all ~24
Recover unknown or leaked state by closing every session owned by this server.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_exchange ~104
Atomically subscribe, write, and collect notifications through one open session.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_write | boolean | – | – |
| base64_value | – | – | – |
| confirm_device | – | – | – |
| duration | number | – | – |
| hex_value | – | – | – |
| notify_characteristic | string | yes | – |
| read_back | boolean | – | – |
| response | boolean | – | – |
| session_id | string | yes | – |
| text_value | – | – | – |
| write_characteristic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_inspect ~26
Discover services on an open BLE session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_list ~24
List open BLE sessions, their devices, idle time, and lease timeout.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_observe ~42
Observe notify/indicate characteristics through one existing session connection.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristics | – | – | – |
| duration | number | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_open ~37
Open a leased connection; timeout applies per backend operation for the session.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_read ~33
Read a characteristic through an open BLE session.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristic | string | yes | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_subscribe ~41
Collect bounded notifications through an open BLE session.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristic | string | yes | – |
| duration | number | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_session_write ~84
Write through an open session with the same explicit write guard.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_write | boolean | – | – |
| base64_value | – | – | – |
| characteristic | string | yes | – |
| confirm_device | – | – | – |
| hex_value | – | – | – |
| read_back | boolean | – | – |
| response | boolean | – | – |
| session_id | string | yes | – |
| text_value | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_subscribe ~52
Collect bounded notifications; timeout is per backend operation, not a total deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| characteristic | string | yes | – |
| device | string | yes | – |
| duration | number | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_unpair ~63
Remove an OS bond for an exact device; unpairing may disconnect existing clients.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_pairing | boolean | – | – |
| confirm_device | – | – | – |
| device | string | yes | – |
| scan_timeout | number | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ble_write ~93
Write with guards; timeout is per backend operation, not a total tool deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_write | boolean | – | – |
| base64_value | – | – | – |
| characteristic | string | yes | – |
| confirm_device | – | – | – |
| device | string | yes | – |
| hex_value | – | – | – |
| read_back | boolean | – | – |
| response | boolean | – | – |
| text_value | – | – | – |
| timeout | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the BLEA MCP server?
BLEA runs locally as a PyPI package, launched with uvx blea. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · blea
claude mcp add nitmi-blea -- uvx blea
What is the BLEA MCP server?
BLEA is an MCP server listed in the public MCP registry as io.github.Nitmi/blea. Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents. This page covers its PyPI package (blea).
Is the BLEA MCP server safe to use?
BLEA scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 BLEA MCP server expose?
BLEA exposes 24 tools: ble_doctor, ble_scan, ble_inspect, ble_probe, ble_capture, and 19 more. Their descriptions and schemas cost roughly 1,607 tokens of context every time the server is loaded.
Is the BLEA MCP server still maintained?
BLEA is still listed as active in the MCP registry. We last reached this channel on 17 October 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 BLEA MCP server under?
BLEA declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.