Is Brightspace MCP safe to use?

Brightspace MCP has an HVTrust score of 42.8/100 (Grade D), ranked #571 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Brightspace MCP?

Brightspace MCP scores 42.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 10 GitHub stars and is categorized under MCP Servers.

Brightspace MCP

JhostinAleck/brightspace-mcp

MCP server for D2L Brightspace with multi-strategy authentication (TOTP, OAuth, browser, etc.), retry/circuit breaker/ca

MCP Servers TypeScript Grade D Listed MIT

42.8/100

Rank #571 of 1283

Compare Brightspace MCP

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 C · 2/5 signals

Last push

2026-08-03 · 9d ago

Recent change

Rank +1

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

Ranked neighbours in MCP Servers

#215 Universal Screenshot MCP — 43.2 (D) → #216 MCP AutoMem — 43.1 (D) → #218 Storybook MCP Addon — 42.8 (D) → #219 Mirroir MCP — 42.7 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-10

Rank Moved

Rank dropped 21 spots (#549 → #570)

2026-08-08

Newly Listed

First tracked at rank #546

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/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 Brightspace MCP View MCP Servers Report missing data

30.1

Activity sub-score · out of 100

#217

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 D 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-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-03

9 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #571

Analysis

HVTrust Dimensions vs MCP Servers

42.8 / 100 · 67.0% confidence

Brightspace MCP MCP Servers average (761 agents)

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

13.2 / 25

8.2 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

3.2 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

11.4 / 20

1.0 below avg 12.4

AdoptionLog-scaled stars · package downloads

2.5 / 20

3.3 below avg 5.8

Activity Inputs

30.1 / 100

StarsRepository reach

6.2 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.1 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

12%

of last 100 commits verified

CI-Tests -1

Dependency-Update-Tool 10

Dangerous-Workflow 10

Code-Review 0

Maintained 10

Token-Permissions 0

Binary-Artifacts 10

SAST 0

CII-Best-Practices 0

Pinned-Dependencies 3

License 10

Fuzzing 0

Signed-Releases 0

Vulnerabilities 0

Security-Policy 0

Branch-Protection 0

Packaging 10

Contributors 3

Is Brightspace MCP safe?

Public trust evidence for Brightspace MCP 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 Brightspace MCP publish package provenance?

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

Does Brightspace MCP have an OpenSSF Scorecard?

Brightspace MCP has an OpenSSF Scorecard score of 4.1/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 Brightspace MCP actively maintained?

Maintained. Last push was 9 days ago.

What license does Brightspace MCP use?

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

Are Brightspace MCP's commits signed?

12% of the last 100 commits to Brightspace MCP 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

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

high confidence

1 tags

Broad capability areas detected.

browser

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 Brightspace MCP?

For maintainers

HVTrust scores Brightspace MCP 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-08-10

Rank Moved

Rank dropped 21 spots (#549 → #570)

2026-08-08

Newly Listed

First tracked at rank #546

GitHub → npm: brightspace-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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