brightspace-mcp-server@5.1.41
CAUTION· not startedPublisher claims: "MCP server for Brightspace (D2L). Check grades, due dates, assignments, announcements, syllabus, rosters and more via Claude, ChatGPT, Cursor, Windsurf, or any MCP client." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try brightspace-mcp-server` runs it now and prints the full answer.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-06 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 3 scenarios · 0 deviationsStatic findings
const ENV_CREDENTIAL = "Nothing to do. This server authenticates with a credential from its configuration (D2L_ACCESS_TOKEN or D2L_SESSION_COOKIE), not with a sign-in it can start. If Brightspace is rFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// runtime idled out. The settings it needs, .env included, are already inFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const kill = (signal) => {Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.env: { ...env, [REEXEC_SENTINEL]: "1" },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return text("Nothing was signed out. This server uses a credential from its configuration (D2L_ACCESS_TOKEN or D2L_SESSION_COOKIE, set in your AI app's client configuration or a .env file), and sign_oFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return new SunySSOFlow({ ...credentials, campus: config.campus });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Never type the password into anything but MUN's own login server.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* The person's last setup step: enter the password, approve sign-in. AlwaysFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// and is deliberately weaker (see .env.example) so it is never the default.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `npx -y brightspace-mcp-server@latest auth` and hands back that process'sFix: Pin versions and sources; vendor anything fetched at install time.export const LOGOUT_COMMAND = `npx -y ${PACKAGE_NAME}@latest auth --logout`;Fix: Pin versions and sources; vendor anything fetched at install time.console.log(yellow(" Could not remove the saved authenticator key. Delete the brightspace-mcp-server entries from your computer's password store."));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* Every npx command here is pinned to @latest deliberately. Invoking npx withFix: Pin versions and sources; vendor anything fetched at install time.const UNEXPECTED_FAILURE = "Could not clear the saved session because of an unexpected error. Nothing more was changed; try again, or run `npx -y brightspace-mcp-server@latest auth --logout` in a termFix: Pin versions and sources; vendor anything fetched at install time.return false; // npx just fetched thisFix: Pin versions and sources; vendor anything fetched at install time.steps.push(fail("app", "No supported AI app found — register `npx -y brightspace-mcp-server@latest` in your app by hand", false));Fix: Pin versions and sources; vendor anything fetched at install time.// open's mode is subject to the umask; chmod is not.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.export const AUTH_COMMAND = `npx -y ${PACKAGE_NAME}@latest auth`;Fix: Pin versions and sources; vendor anything fetched at install time.* The MCP server is launched as `npx -y brightspace-mcp-server@latest`, so itFix: Pin versions and sources; vendor anything fetched at install time.// If npx itself cannot start, run the stale copy rather than failing.Fix: Pin versions and sources; vendor anything fetched at install time.* a number off the screen. A shorter parent budget would kill the child in theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.export const SETUP_COMMAND = `npx -y ${PACKAGE_NAME}@latest setup`;Fix: Pin versions and sources; vendor anything fetched at install time./** watchAttention is armed once per child; a second timer could kill a live sign-in. */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for brightspace-mcp-server@5.1.41 as of 8d ago. This is the package itself, not its dependencies.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Prompting user to enter sensitive credentials≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Unclaimed publisher≈ +8 on the totalClaim rohanmuppa: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.