harald
Related Servers
Alternatives to harald
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceDrive a Flipper Zero wirelessly over Bluetooth LE from Claude.381MIT
- AlicenseBqualityCmaintenanceA lightweight Bluetooth Low Energy debug MCP server for AI agents. It provides 21 tools for BLE scanning, connection, GATT read/write, descriptor access, MTU query, notification subscription, device recon, and engine diagnostics.2115 PyPIApache 2.0
- AlicenseAqualityAmaintenanceReverse engineer Windows-only USB gadgets: capture vendor-app traffic, infer the protocol with frame-level evidence, and generate an open Python/pyusb driver. Replay needs human confirmation.92MIT
- AlicenseNot gradedqualityBmaintenanceExposes 238 schema-typed tools over streamable-HTTP MCP that let a client drive a Flipper Zero, an AWOK Biscuit (ESP32-C5) and an ESP32 Marauder — scanning, screen mirroring, storage, and other device operations — from natural-language or direct tool calls. Transmit/attack tools stay behind an explicit human confirmation gate.MIT
- AlicenseAqualityCmaintenanceA stateful Bluetooth Low Energy (BLE) MCP server that enables AI agents to scan, connect, read/write characteristics, and subscribe to notifications on BLE devices.3577 PyPI19MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Bluetooth audio devices via MCP tools, including battery status, connect/disconnect, find-my, and snoop decoding.MIT
TDQS
Scored across 18 tools
Most tools are cleanly separated by transport (BLE vs classic) and action (scan, connect, read_char, write_char, subscribe, classic_send, classic_listen). There is mild overlap among the three listing/discovery tools (scan, list_devices, classic_devices) and between open_capture and analyze_apk, but descriptions make the boundaries clear.
All names use snake_case consistently, with a sensible classic_* namespace for the classic transport tools. However, the convention is a mix of verb_noun (read_char, save_note), noun_action (classic_send, classic_devices), and bare verbs (scan, connect, subscribe, diff), so it is not a single predictable pattern.
18 tools is on the heavier side but each maps to a distinct capability (transport ops, capture analysis, crypto analysis, APK analysis, notes/library). The breadth is justified by the varied reverse-engineering workflow rather than being padding.
Covers the full BLE and classic lifecycle (scan, connect, read/write/subscribe/send/listen) plus strong analysis tooling (captures, diff, checksums, key trial, APK static analysis) and a notes/device library. Minor gaps like no explicit BLE disconnect/unsubscribe or device-library registration keep it from a 5.