F
Warning
10/100
10 hours ago

sandbase-harness

Local-first AI agent runtime with sandboxed sessions, MCP tools, memory, credentials, audit/replay, and a built-in console. Run OpenAI, Anthropic, MiniMax, DeepSeek V4, and OpenAI-compatible models on your infrastructure.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

sandbaseai

Source: github_topic

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

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

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

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highnanoid@3.3.15GHSA-28wg-ghj8-5hjv

nanoid: non-secure generators can loop indefinitely with negative size

highnanoid@3.3.15GHSA-2v37-7h3g-55p8

nanoid: custom generators can loop indefinitely when size is zero

highvite@5.4.21GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

mediumvite@5.4.21GHSA-4w7w-66w2-5vf9

Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

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.
🔐 secretMANAGED_AGENTS_API_KEYFor an authenticated remote runtime, also pass . The
configMANAGED_AGENTS_CORS_ORIGINS
🔐 secretMANAGED_AGENTS_ENVIRONMENT_KEY
configMANAGED_AGENTS_HOME
configMANAGED_AGENTS_LOG_FORMAT
configMANAGED_AGENTS_LOG_LEVEL
🔐 secretMANAGED_AGENTS_SECRET_KEY
configMANAGED_AGENTS_URLexport =http://127.0.0.1:3000
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/6 tools missing one or more hints — list_agents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

5/6 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 0/6 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

18 child_process/subprocess calls in production code — runs shell commands (src/cli/worker-commands.ts:100, src/sandbox/docker-provider.ts:32, src/sandbox/docker-provider.ts:78)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (MANAGED_AGENTS_ENVIRONMENT_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Production dependencies are patched

0 critical, 2 high severity in production deps — nanoid@3.3.15 (high), nanoid@3.3.15 (high)

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

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 9 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 Verified](https://m8ven.ai/badge/mcp/sandbaseai-sandbase-harness-wfy0es?variant=verified)](https://m8ven.ai/mcp/sandbaseai-sandbase-harness-wfy0es)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 841ac14e1b5a37b52a97d89eebe19c030ee4f1c6
code hash: 8a6d5739fa69d31f7dee4df785fc92792c6a8169dec1898547011cba62aa0223
verified: 8/19/2026, 7:00:31 PM
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