Bluetooth Specifications MCP Server

The materials explicitly state that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential exposure and abuse risk appears low.

No remote endpoints are declared in the materials, and the description focuses on searching Bluetooth specification PDFs. Based on the available facts, there is no explicit user-data egress path, though the missing README means runtime downloads of models or documents cannot be further verified.

System checks confirm code-execution capability. As an MCP tool, this implies running a local service/process and handling queries on the host. That inherent capability alone does not justify a high-risk rating, but it should be run in a constrained environment and its actual dependencies and startup behavior should be reviewed.

Based on its stated function, it likely needs access to Bluetooth specification PDFs and related index data, which may involve reading local documents and generating search indexes. The provided materials do not show a need for file permissions beyond that declared purpose, nor any explicit requirement to write into sensitive system locations.

Positive factors include an auditable open-source repository and a BSD 3-Clause license, which reduce risk. However, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README in the provided materials, so transparency and maturity are limited and the source code and dependencies should be reviewed directly.