Is Ble MCP Server safe to use?

Ble MCP Server has an HVTrust score of 52.6/100 (Grade C), ranked #824 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Ble MCP Server?

Ble MCP Server scores 52.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 17 GitHub stars and is categorized under MCP Servers.

Ble MCP Server

es617/ble-mcp-server

Bluetooth Low Energy (BLE) MCP server for Claude Code and other MCP-compatible agents.

MCP Servers Python Grade C Listed MIT

52.6/100

Rank #824 of 1328

Compare Ble MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-03-30 · 162d ago

Recent change

Rank +7

Is Ble MCP Server safe? Ble MCP Server scores 52.6/100 (Grade C), ranked #824 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.5/10; 2% of recent commits are signed; last pushed 2026-03-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#450 SharpLens — 52.7 (C) → #451 Smart Connections MCP — 52.7 (C) → #453 PostgreSQL MCP Server — 52.5 (C) → #454 Lineai MCP Server — 52.5 (C) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-08

Rank Moved

Rank dropped 12 spots (#812 → #824)

2026-09-07

Rank Moved

Rank dropped 35 spots (#777 → #812)

2026-09-06

Rank Moved

Rank dropped 14 spots (#763 → #777)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 162 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Ble MCP Server View MCP Servers Report missing data

12.2

Activity sub-score · out of 100

#452

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-03-30

162 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼12

was #812

Analysis

HVTrust Dimensions vs MCP Servers

52.6 / 100 · 100.0% confidence

Ble MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.0 / 25

2.1 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.5 / 17

0.5 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

1.2 / 20

11.0 below avg 12.2

AdoptionLog-scaled stars · package downloads

4.9 / 20

2.0 below avg 6.9

Activity Inputs

12.2 / 100

StarsRepository reach

7.5 / 30

FreshnessLast push recency

2.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 6, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is Ble MCP Server safe?

Public trust evidence for Ble MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Ble MCP Server publish package provenance?

Yes. Ble MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Ble MCP Server have an OpenSSF Scorecard?

Ble MCP Server has an OpenSSF Scorecard score of 3.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Ble MCP Server actively maintained?

Slowing down. Last push was 162 days ago — keep an eye on whether activity resumes.

What license does Ble MCP Server use?

Ble MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Ble MCP Server's commits signed?

1% of the last 100 commits to Ble MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Ble MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Ble MCP Server?

For maintainers

HVTrust scores Ble MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-08

Rank Moved

Rank dropped 12 spots (#812 → #824)

2026-09-07

Rank Moved

Rank dropped 35 spots (#777 → #812)

2026-09-06

Rank Moved

Rank dropped 14 spots (#763 → #777)

2026-09-05

Rank Moved

Rank dropped 75 spots (#688 → #763)

2026-09-04

Rank Moved

Rank dropped 22 spots (#666 → #688)

2026-09-03

Rank Moved

Rank dropped 37 spots (#629 → #666)

2026-09-02

Rank Moved

Rank dropped 38 spots (#591 → #629)

2026-09-01

Rank Moved

Rank dropped 19 spots (#572 → #591)

2026-08-31

Rank Moved

Rank dropped 33 spots (#539 → #572)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 138 spots (#677 → #539)

2026-08-30

HVTrust Changed

HVTrust up 7.3pts (46.4 → 53.7)

2026-08-29

Rank Moved

Rank dropped 44 spots (#633 → #677)

2026-08-28

Rank Moved

Rank dropped 22 spots (#611 → #633)

2026-08-27

Rank Moved

Rank dropped 13 spots (#598 → #611)

2026-08-26

Rank Moved

Rank dropped 88 spots (#510 → #598)

2026-08-24

Rank Moved

Rank dropped 15 spots (#496 → #511)

2026-08-22

Rank Moved

Rank rose 10 spots (#510 → #500)

2026-08-19

Rank Moved

Rank dropped 14 spots (#496 → #510)

2026-08-17

Rank Moved

Rank rose 14 spots (#508 → #494)

2026-08-16

Rank Moved

Rank dropped 10 spots (#498 → #508)

2026-08-13

Rank Moved

Rank dropped 15 spots (#481 → #496)

2026-08-10

Rank Moved

Rank dropped 24 spots (#469 → #493)

2026-08-08

Newly Listed

First tracked at rank #466

GitHub → PyPI: ble-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ble-mcp-server.svg)](https://hvtracker.net/agents/ble-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/ble-mcp-server"><img src="https://hvtracker.net/badge/ble-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON