labbench (yunxingl/mcp_remote_sandbox) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
—
Grade pending
5 days ago

labbench

Enables Claude Code to browse coursework, manage user workspaces, run sandboxed tests, post hints, and assign new projects in LabBench.

→ yunxingl/mcp_remote_sandbox· listed on glama

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

yunxingl

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: OPENROUTER_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: MCP_TOKEN, MODAL_TOKEN_SECRET, OPENROUTER_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 high1 medium1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalnext-auth@5.0.0-beta.29GHSA-7rqj-j65f-68wh

Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass

criticalnext-auth@5.0.0-beta.29GHSA-8fpg-xm3f-6cx3

Auth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error)

highnext-auth@5.0.0-beta.29GHSA-xmf8-cvqr-rfgj

Auth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers

mediumnext-auth@5.0.0-beta.29GHSA-5jpx-9hw9-2fx4

NextAuthjs Email misdelivery Vulnerability

lownext-auth@5.0.0-beta.29GHSA-x445-f3h2-j279

Auth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configALLOWED_EMAILSGoogle login, allowlist-only — only emails in can sign in.
configAUTH_URL
configLOCAL_RUNNER_DIR
🔐 secretMCP_TOKEN6. — openssl rand -hex 32; static bearer token for the MCP
configMODAL_APP_NAME
configMODAL_TOKEN_ID5. Modal — /MODAL_TOKEN_SECRET
🔐 secretMODAL_TOKEN_SECRET5. Modal — MODAL_TOKEN_ID/
configNEXTAUTH_URL
🔐 secretOPENROUTER_KEY4. OpenRouter — (from [openrouter.ai/keys](https://openrouter.ai/keys))
configOPENROUTER_MODELenables the in-site tutor chat; picks the model
configRUNNER_BACKENDauto, problems run on Modal when it's configured and
// quality suggestions

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Production dependencies are patched

2 critical, 1 high severity in production deps — next-auth@5.0.0-beta.29 (critical), next-auth@5.0.0-beta.29 (critical)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

3/17 production deps abandoned (no release in 2+ years): rehype-raw@2023-11-20 (2.8y), remark-math@2023-11-20 (2.8y), rehype-katex@2024-08-19 (2.1y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/yunxingl/mcp_remote_sandbox)](https://m8ven.ai/mcp/yunxingl/mcp_remote_sandbox)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8bac8a3850f0db5f3854c5670b28d8e518744712
code hash: 8fedbf9f394c4a4471a2792bc5e442ebdaf45061096fe9061a5f07e5fa3cf2ab
verified: 9/7/2026, 7:34:04 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client