Is BLS OEWS safe to use?

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

What is the trust score for BLS OEWS?

BLS OEWS scores 63.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

BLS OEWS

1102tools/federal-contracting-mcps

Nine deterministic MCP servers for federal procurement data, pricing, regulations, rulemaking, and Acquisition.gov.

MCP Servers Python Grade C Listed MIT

63.6/100

Rank #368 of 1320

Compare BLS OEWS

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 B · 3/5 signals

Last push

2026-08-27 · 8d ago

Recent change

Rank +7

Is BLS OEWS safe? BLS OEWS scores 63.6/100 (Grade C), ranked #368 of 1320 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.9/10; 1% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#172 JS Reverse MCP — 63.6 (C) → #173 Excel Vision MCP — 63.6 (C) → #175 Codex Control Plane MCP — 63.6 (C) → #176 Git MCP Server — 63.4 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 11 spots (#357 → #368)

2026-09-03

Rank Moved

Rank dropped 18 spots (#339 → #357)

2026-09-02

Rank Moved

Rank dropped 13 spots (#326 → #339)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/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.

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

58.9

Activity sub-score · out of 100

#174

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

Activity & Reach

Stars

Forks

Last Push

2026-08-27

8 days ago

Commits (4 wk)

Downloads (7d)

343

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼11

was #357

Analysis

HVTrust Dimensions vs MCP Servers

63.6 / 100 · 100.0% confidence

BLS OEWS MCP Servers average (778 agents)

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

12.4 / 25

2.8 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

18.8 / 20

6.6 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.6 / 20

in line with avg 6.3

Activity Inputs

58.9 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

22.9 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is BLS OEWS safe?

BLS OEWS 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 BLS OEWS publish package provenance?

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

Does BLS OEWS have an OpenSSF Scorecard?

BLS OEWS has an OpenSSF Scorecard score of 3.9/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 BLS OEWS actively maintained?

Maintained. Last push was 8 days ago.

What license does BLS OEWS use?

BLS OEWS ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are BLS OEWS's commits signed?

1% of the last 100 commits to BLS OEWS 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

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

Warning

1 package source mismatch detected

Detailed evidence is not shown in the public view.

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

How this surface has changed

Detected changes to BLS OEWS'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.

2026-08-24

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-08-15

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-15

Activity Resumed

Activity resumed

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain BLS OEWS?

For maintainers

HVTrust scores BLS OEWS 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-04

Rank Moved

Rank dropped 11 spots (#357 → #368)

2026-09-03

Rank Moved

Rank dropped 18 spots (#339 → #357)

2026-09-02

Rank Moved

Rank dropped 13 spots (#326 → #339)

2026-09-01

Rank Moved

Rank dropped 14 spots (#312 → #326)

2026-08-31

Rank Moved

Rank dropped 35 spots (#277 → #312)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-29

Rank Moved

Rank rose 184 spots (#463 → #279)

2026-08-29

HVTrust Changed

HVTrust up 8.2pts (56.4 → 64.6)

2026-08-26

Rank Moved

Rank dropped 44 spots (#403 → #447)

2026-08-24

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-08-24

Rank Moved

Rank dropped 176 spots (#225 → #401)

2026-08-24

HVTrust Changed

HVTrust down 8.6pts (64.9 → 56.3)

2026-08-22

Rank Moved

Rank rose 19 spots (#249 → #230)

2026-08-19

Rank Moved

Rank dropped 13 spots (#244 → #257)

2026-08-18

Rank Moved

Rank rose 10 spots (#254 → #244)

2026-08-17

Rank Moved

Rank rose 43 spots (#297 → #254)

2026-08-16

Rank Moved

Rank rose 56 spots (#353 → #297)

2026-08-16

HVTrust Changed

HVTrust up 3.3pts (58.9 → 62.2)

2026-08-15

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-15

Activity Resumed

Activity resumed

2026-08-15

Grade Changed

Trust grade D → C

2026-08-15

Rank Moved

Rank rose 128 spots (#481 → #353)

2026-08-15

HVTrust Changed

HVTrust up 10.7pts (48.2 → 58.9)

2026-08-15

Activity Score Changed

Activity score up 30pts (20 → 50)

2026-08-13

Rank Moved

Rank dropped 14 spots (#467 → #481)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Rank Moved

Rank rose 20 spots (#487 → #467)

2026-08-10

Rank Moved

Rank dropped 13 spots (#473 → #486)

2026-08-08

Newly Listed

First tracked at rank #458

GitHub → PyPI: bls-oews-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/bls-oews.svg)](https://hvtracker.net/agents/bls-oews)
            
HTML:
            <a href="https://hvtracker.net/agents/bls-oews"><img src="https://hvtracker.net/badge/bls-oews.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