Bagel
Query robotics, drone, and IoT data in plain English through an MCP server, with an intelligent edge data reduction pipeline that keeps only the data that matters.
Is Bagel safe? Promising trust profile, but some evidence still deserves review.
Compare Bagel
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Bagel scores 62.0/100 (Grade C), ranked #578 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.3/10; 43% of recent commits are signed; last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →
How Bagel could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 6.3 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Token-Permissions 0 +5.6 → 67.6 B · #238 of 778
- Sign every commit43% signed today +2.9 → 64.9 C · #276 of 778
How Bagel compares in MCP Servers
- #326 Glade MCP 62.1 +0.1
- #327 Rootly MCP Server 62.0 ±0
- #328 Bagel 62.0 this agent
- #329 MCP Server for OSCAL 62.0 ±0
- #330 Galaxy MCP 61.9 −0.1
Bars show each HVTrust score; the tick marks Bagel’s 62.0.
Where the 62.0 comes from
HVTrust dimensions vs the MCP Servers average
62.0 / 100 · 100.0% confidenceBagel MCP Servers average (778 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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
72.5 / 100Supply Chain Trust
Common questions about Bagel
Does Bagel publish package provenance?
Does Bagel have an OpenSSF Scorecard?
Is Bagel actively maintained?
What license does Bagel use?
Are Bagel'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 Bagel'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 Bagel?
For maintainers
HVTrust scores Bagel 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/bagel)
<a href="https://hvtracker.net/agents/bagel"><img src="https://hvtracker.net/badge/bagel.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON