Is Bagel safe to use?

Bagel has an HVTrust score of 59.2/100 (Grade C), ranked #471 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Bagel?

Bagel scores 59.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 396 GitHub stars and is categorized under MCP Servers.

Bagel

Extelligence-ai/bagel

Query robotics, drone, and IoT data in plain English through an MCP server, with an intelligent edge data reduction pipe

MCP Servers Python Grade C Listed Apache-2.0

59.2/100

Rank #471 of 1320

Compare Bagel

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Rank +4

Is Bagel safe? Bagel scores 59.2/100 (Grade C), ranked #471 of 1320 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 5.2/10; 35% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#213 Buildkite MCP Server — 59.7 (C) → #214 Google Health MCP — 59.4 (C) → #216 Logic Pro MCP — 59.1 (C) → #217 MCP ZAP Server — 59.0 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-03

Rank Moved

Rank dropped 23 spots (#444 → #467)

2026-09-01

Rank Moved

Rank dropped 12 spots (#425 → #437)

2026-08-31

Rank Moved

Rank dropped 30 spots (#395 → #425)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

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

72.5

Activity sub-score · out of 100

#215

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 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

2026-08-16 2026-09-04

Activity & Reach

Stars

396

Forks

Last Push

2026-09-03

yesterday

Commits (4 wk)

156

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #467

Analysis

HVTrust Dimensions vs MCP Servers

59.2 / 100 · 100.0% confidence

Bagel MCP Servers average (778 agents)

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

8.2 / 25

1.3 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.9 / 17

1.1 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.2 / 20

in line with avg 6.2

Activity Inputs

72.5 / 100

StarsRepository reach

15.6 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

6.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.2 / 10

OpenSSF Scorecard · scanned Aug 30, 2026

Signed Commits

35%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Bagel safe?

Bagel has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Bagel publish package provenance?

No published build provenance is currently detected for Bagel. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Bagel have an OpenSSF Scorecard?

Bagel has an OpenSSF Scorecard score of 5.2/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 Bagel actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Bagel use?

Bagel ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Bagel's commits signed?

35% of the last 100 commits to Bagel 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

medium confidence

Implemented

Bagel appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-03

Rank Moved

Rank dropped 23 spots (#444 → #467)

2026-09-01

Rank Moved

Rank dropped 12 spots (#425 → #437)

2026-08-31

Rank Moved

Rank dropped 30 spots (#395 → #425)

2026-08-30

Rank Moved

Rank rose 19 spots (#414 → #395)

2026-08-29

Rank Moved

Rank dropped 11 spots (#403 → #414)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.2/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 460 spots (#850 → #390)

2026-08-26

HVTrust Changed

HVTrust up 34.2pts (24.7 → 58.9)

2026-08-18

Rank Moved

Rank rose 25 spots (#871 → #846)

2026-08-17

Rank Moved

Rank rose 12 spots (#883 → #871)

2026-08-16

Newly Listed

First tracked at rank #883

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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