MCP.Market

BLEA MCP server

by Nitmi·io.github.Nitmi/blea·v0.7.0·11 stars

Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

11 stars63 downloads/wk

Reviews

Write one

Nobody has reviewed BLEA yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

BLEA tools (24, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • ble_capture

    Save a validated read-only BLE evidence package as .blea.jsonl.

  • ble_diff

    Compare two validated BLEA evidence files without accessing Bluetooth hardware.

  • ble_doctor

    Check whether the local Bluetooth adapter and OS BLE backend are usable.

  • ble_exchange

    Subscribe first, perform one guarded write, then collect resulting notifications.

  • ble_inspect

    Discover GATT; timeout applies separately to scan, connect, and GATT operations.

  • ble_observe

    Observe notify/indicate characteristics on one connection for a bounded duration.

  • ble_pair

    Pair an exact id:<identifier> with guards; optional six-digit PIN is Windows-only.

  • ble_probe

    Read one GATT page; inspect read_page and follow next_read_offset until null.

  • ble_read

    Read a characteristic; timeout applies separately to scan, connect, and GATT operations.

  • ble_replay

    Replay scan/inspect/probe/read/subscribe/observe/run from evidence without BLE hardware.

  • ble_scan

    Scan nearby BLE advertisements and return stable structured evidence.

  • ble_session_close

    Disconnect and forget an open BLE session.

  • ble_session_close_all

    Recover unknown or leaked state by closing every session owned by this server.

  • ble_session_exchange

    Atomically subscribe, write, and collect notifications through one open session.

  • ble_session_inspect

    Discover services on an open BLE session.

  • ble_session_list

    List open BLE sessions, their devices, idle time, and lease timeout.

  • ble_session_observe

    Observe notify/indicate characteristics through one existing session connection.

  • ble_session_open

    Open a leased connection; timeout applies per backend operation for the session.

  • ble_session_read

    Read a characteristic through an open BLE session.

  • ble_session_subscribe

    Collect bounded notifications through an open BLE session.

  • ble_session_writewrite action

    Write through an open session with the same explicit write guard.

  • ble_subscribe

    Collect bounded notifications; timeout is per backend operation, not a total deadline.

  • ble_unpairwrite action

    Remove an OS bond for an exact device; unpairing may disconnect existing clients.

  • ble_writewrite action

    Write with guards; timeout is per backend operation, not a total tool deadline.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan25 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 16 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How BLEA compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 93% of 48,243 servers
Tools
24
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
11
more than 88% of 28,706 servers
Downloads a week
63
more than 49% of 12,306 servers with a package

What its tools let an agent do: 21 read · 3 change

Release history: 2 versions in the registry since 2026-09-09, latest 2026-09-29, typically one every 20 days.

Install BLEA in Claude Code, Cursor or VS Code

claude mcp add blea -- uvx blea
Add to Cursor

What the publisher says

From the BLEA repository's README, as published. We do not edit it. Read it on GitHub

BLEA

<!-- mcp-name: io.github.Nitmi/blea -->

BLEA — Bluetooth Low Energy Automation — is a universal Agent Plugin for safe, deterministic BLE work. It gives AI agents a portable Skill, a machine-readable CLI, a local MCP server, guarded automation, and offline evidence capture, diff, and replay.

The project is designed for the BLE work agents repeatedly need: checking OS Bluetooth access, finding the right nearby device, discovering GATT services, preserving and comparing raw byte evidence, reading and subscribing before changing state, and making writes only after explicit authorization.

The ble executable is the shared runtime. Regular subcommands use the CLI surface; ble mcp starts the stdio MCP server. The MCP protocol is therefore a first-class interface, not a second tool hidden inside an unrelated CLI product.

Install

BLEA requires Python 3.10 or newer. Bluetooth access is provided by the operating system through Bleak.

Quick install with an Agent prompt

Give this prompt to an Agent with shell access:

Read https://github.com/Nitmi/blea and follow its README to install BLEA for me.

For manual installation, use the detailed paths below.

Install the latest published Python runtime from PyPI:

uv tool install blea
ble --help

For Codex, install the public Git marketplace package after the runtime:

codex plugin marketplace add Nitmi/blea
codex plugin add blea@blea

To install only the portable Agent Skill with the Skills CLI:

npx skills add Nitmi/blea --skill ble

For OpenClaw, install the same portable Skill from its public ClawHub listing:

openclaw skills install @nitmi/blea
# Or use the registry CLI directly:
clawhub install @nitmi/blea

The Skill teaches the workflow and safety policy; it does not install the Python runtime. Install blea from PyPI as shown above before asking an agent to access live Bluetooth hardware or start the local MCP server. The source Skill is skills/ble/SKILL.md, and the public ClawHub release is @nitmi/blea.

Start a new Agent task after installation. The marketplace package supplies the BLE Skill and MCP declaration; it does not install the Python runtime or operating-system Bluetooth permissions. See docs/installation.md for the release-tag, legacy 0.6.0 bridge, and update procedure.

From a checkout, install the command runtime directly from the working tree:

uv tool install --editable .
ble --version

For repository development:

uv sync --extra dev
uv run ble --help

Standalone Windows release

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

BLEA: common questions

Is BLEA MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the BLEA safety report
How do I install BLEA?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does BLEA need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is BLEA maintained?
The last commit was 37 days ago (2026-09-29). The latest release is v0.7.0.
How does BLEA compare with other MCP servers?
safety score 92/100 (higher than 93% of 48,243 servers); tools 24 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.