updated 2026-09-26 06:32 UTC

Brightspace MCP

JhostinAleck/brightspace-mcp

MCP server for D2L Brightspace with multi-strategy authentication (TOTP, OAuth, browser, etc.), retry/circuit breaker/cache tiers, and opt-in write operations.

MCP Servers TypeScript Listed MIT

Is Brightspace MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.4 / 10
Provenance Attested
Signed commits 12%
Last push 54d ago
Compare Brightspace MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Brightspace MCP scores 59.9/100 (Grade C), ranked #634 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.4/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 →

How Brightspace MCP compares in MCP Servers

  1. #354 Wavyrai reMarkable MCP Server 59.9 ±0
  2. #355 OpenResearch MCP 59.9 ±0
  3. #356 Brightspace MCP 59.9 this agent
  4. #357 MCP Imagenate 59.6 −0.3
  5. #358 Funplay Cocos MCP 59.6 −0.3

Bars show each HVTrust score; the tick marks Brightspace MCP’s 59.9.

Where the 59.9 comes from

HVTrust dimensions vs the MCP Servers average

59.9 / 100 · 100.0% confidence

Brightspace MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.3 / 25
2.0 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.8 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
8.4 / 20
3.7 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.1 / 20
2.1 below avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/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.
Refresh maintenance signals The repo was last pushed 54 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Brightspace MCP View MCP Servers Report missing data
25.7
Activity sub-score · out of 100
#356
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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 54 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
12
Forks
1
Last Push
2026-08-03
54 days ago
Commits (4 wk)
0
Downloads (7d)
61
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #632

Analysis

Activity Inputs

25.7 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
17.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.4 / 10
OpenSSF Scorecard · scanned Sep 12, 2026
Signed Commits
12%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Common questions about Brightspace MCP

Brightspace MCP 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 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 3.4/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?
Slowing down. Last push was 54 days ago — keep an eye on whether activity resumes.
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
How this surface has changed

Detected changes to Brightspace MCP'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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

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
Rank 19Listed 2HVTrust 2Grade 2Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 567 spots (#1193 → #626)
2026-09-23
HVTrust Changed
HVTrust up 40.6pts (19.5 → 60.1)
2026-09-22
Newly Listed
First tracked at rank #1193
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 20 spots (#571 → #591)
2026-09-11
Rank Moved
Rank dropped 12 spots (#559 → #571)
2026-09-08
Rank Moved
Rank dropped 14 spots (#541 → #555)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 554 spots (#1095 → #541)
2026-09-07
HVTrust Changed
HVTrust up 20.6pts (40.6 → 61.2)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1079 → #1095)
2026-09-05
Rank Moved
Rank dropped 42 spots (#1037 → #1079)
2026-09-04
Rank Moved
Rank dropped 23 spots (#1014 → #1037)
2026-09-03
Rank Moved
Rank dropped 57 spots (#957 → #1014)
2026-09-02
Rank Moved
Rank dropped 56 spots (#901 → #957)
2026-09-01
Rank Moved
Rank dropped 33 spots (#868 → #901)
2026-08-31
Rank Moved
Rank dropped 29 spots (#839 → #868)
2026-08-30
Rank Moved
Rank dropped 34 spots (#805 → #839)
2026-08-29
Rank Moved
Rank dropped 46 spots (#759 → #805)
2026-08-28
Rank Moved
Rank dropped 28 spots (#731 → #759)
2026-08-27
Rank Moved
Rank dropped 24 spots (#707 → #731)
2026-08-26
Rank Moved
Rank dropped 113 spots (#594 → #707)
2026-08-13
Rank Moved
Rank dropped 10 spots (#567 → #577)
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
HVTrust 59.9 Grade C
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