Ble MCP Server
Bluetooth Low Energy (BLE) MCP server for Claude Code and other MCP-compatible agents.
Is Ble MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Ble MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Ble MCP Server scores 51.7/100 (Grade C), ranked #892 of 1325 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 →
How Ble MCP Server compares in MCP Servers
- #504 Newsmcp 51.8 +0.1
- #505 Lunch Money 51.7 ±0
- #506 Ble MCP Server 51.7 this agent
- #507 OSS Snowflake MCP Server 51.7 ±0
- #508 Codex MCP Go 51.7 ±0
Bars show each HVTrust score; the tick marks Ble MCP Server’s 51.7.
Where the 51.7 comes from
HVTrust dimensions vs the MCP Servers average
51.7 / 100 · 100.0% confidenceBle MCP Server MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
9.9 / 100Supply Chain Trust
Common questions about Ble MCP Server
Does Ble MCP Server publish package provenance?
Does Ble MCP Server have an OpenSSF Scorecard?
Is Ble MCP Server actively maintained?
What license does Ble MCP Server use?
Are Ble MCP Server's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Ble MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/ble-mcp-server)
<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
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