SandBase Harness: DevOps runtime and MCP bridge discovery #116
Replies: 21 comments
|
Quick start for platform and DevOps users: docker pull ghcr.io/sandbaseai/sandbase-harness:0.3.8Then follow the MCP installation guide to connect the bridge to an MCP client. The current bridge exposes six tools for session lifecycle, tool execution, state, artifacts, and audit/replay workflows. For evaluation, start with the release notes and security boundary. Docker, Kubernetes, and worker backends have different isolation properties; this project does not claim universal microVM or kernel isolation. |
|
Documentation correction: the current installation guide is https://github.com/sandbaseai/sandbase-harness/blob/main/docs/installation.md. The earlier |
|
Promotion update (2026-08-31): current review submissions include Awesome MCP List #408, Awesome Agent Infra #2, Awesome Self-Hosted Agents #6, Awesome AI Automation #3, and Awesome Agent Services #8. These are review submissions, not endorsements or security certifications. The canonical project, v0.3.8 release, installation guide, and sandbox boundary remain the source of truth. |
|
推广进展更新（2026-08-31）：\n\n近期新增并已提交以下公开目录审核：\n\n- Awesome MCP Collection #38\n- Cue OS Awesome Agent OS #2\n- Awesome AI Coding Sandboxes #14\n- Awesome MCP Servers for DevOps #75\n\n这些提交均使用官方仓库、v0.3.8 发布版本和安装文档作为来源，并已披露项目维护关系。它们目前均处于待维护者审核状态，不代表已合并、官方背书或安全认证；沙箱隔离能力取决于所选后端和部署配置。 |
|
推广进展更新（2026-08-31，补充）：\n\n本轮已核验并跟进以下运行时、安全与运维生态入口：\n\n- Awesome Agent Cortex #73\n- Awesome Autonomous Ops #35\n- Awesome Agentic Hardening #5\n- Awesome Agent Harnesses #2\n- Awesome X-Ops #250\n\n这些入口均使用官方仓库、v0.3.8 发布版本和安装/后端文档作为核验来源，并已披露维护关系。各目录的收录仍处于外部审核阶段，不代表已合并、官方背书或安全认证；隔离能力取决于所选 sandbox 后端和部署配置。 |
|
推广更新（2026-08-31）：DeepSeek Harness 双语开发者预览文章已更新到 SandBase Harness v0.3.8，并完成 Cloudflare 部署。\n\n- English article\n- 中文文章\n- merged blog PR #273\n\n两页均已核验返回 HTTP 200，文章中的版本、安装文档和集成链接均指向当前来源。博客中的审计研究文章仍因缺少专属持久化封面与三张证据截图而待补，不将其标记为已完成。 |
|
推广状态核验（2026-08-31）：以下三个目录收录已实际合并并可公开查看：\n\n- Awesome Agent Runtime #15\n- Awesome Native Agent Platforms #1\n- awesome-mcp-servers #45\n\n它们使用当前仓库/来源链接；目录收录不代表官方背书或安全认证，隔离能力仍取决于所选后端和部署配置。 |
|
新增推广提交（2026-08-31）：MCP Find PR #171 已提交，将官方 SandBase Harness Docker bridge（ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8）加入其 community registry。\n\n条目使用 Apache-2.0 官方仓库和事实型 devtools 描述，并已披露维护关系及 backend-dependent isolation 边界。目前 Vercel 预览因授权失败而处于不稳定状态，等待目录维护者处理；尚未声称已合并或已公开收录。 |
|
新增推广提交（2026-08-31）：MCP-Directory PR #5 已创建，按其贡献指南同时更新交互式 index.html 和 README，使用官方 GHCR 0.3.8 镜像及 Docker 安装命令。\n\nPR 当前为 clean/mergeable，无失败检查；等待外部维护者审核合并。条目已披露维护关系，并明确隔离能力取决于所选 backend 和部署配置，不构成安全认证。 |
|
新增推广提交（2026-08-31）：MCP-Directory PR #5 已按该目录贡献指南，同时更新交互式 index.html 和 README，使用官方 GHCR 0.3.8 镜像及 Docker 安装命令。\n\nPR 当前为 clean/mergeable，无失败检查；等待外部维护者审核合并。条目已披露维护关系，并明确隔离能力取决于所选 backend 和部署配置，不构成安全认证。 |
|
新增独立安全核验入口（2026-08-31）：已向 MCPRadar Issue #8 提交 SandBase Harness MCP Bridge 扫描请求。\n\n请求提供了官方 Registry/源码链接和不含凭证的 Docker handshake 命令，并注明 session 调用可能需要用户自己的 API URL/API key。该申请仅请求人工扫描与排行榜评估，不代表已有安全评分、背书或扫描结果。 |
|
维护与推广同步（2026-08-31）：安全 PR #117 已合并到 main，更新 prefix-safe-json 到 0.4.3 安全版本，并加入 post-terminal authority 回归测试。\n\n维护者在隔离 worktree 验证通过：源码类型检查、相关 11 个测试、runtime/Console 构建、package check、release smoke。完整测试套件中既有的环境限制仍按 PR 说明保留，没有被隐藏。 |
|
新增主流 MCP 目录提交（2026-08-31）：Awesome MCP Servers PR #13240 已将 SandBase Harness 加入 Developer Tools，使用官方 Docker bridge 命令和 backend-dependent isolation 说明。\n\n其 check-submission 自动检查已通过，GitHub 状态为 clean/mergeable。当前账号没有该上游仓库的合并权限，已保留为等待维护者合并，不做越权操作。 |
|
Promotion follow-up (2026-08-31): the SandBase Harness MCP bridge was also submitted to BrethofAI/awesome-mcp-servers. The maintainer follow-up includes the current v0.3.8 release, published GHCR image, six-tool scope, installation guide, and the backend-dependent isolation qualification; directory review is pending. Separately, Awesome MCP Servers PR #13240 remains clean/mergeable but its automated gate now requires a Glama listing and score badge; that one-time GitHub OAuth step is still pending, so no Glama score is claimed. |
|
Promotion follow-up (2026-08-31): a new focused directory submission is open at HabitoAI/awesome-mcp-servers PR #37. It adds one factual SandBase Harness entry under Developer Tools and links the official Apache-2.0 source, v0.3.8 release, installation guide, and published GHCR bridge image. GitHub reports the PR as clean and mergeable; maintainer review is pending. |
|
Promotion follow-up (2026-08-31): submitted a distinct SandBase Harness entry to the active MCP Hub/mcpdir intake issue #20. The existing #19 entry is for SandBase CLI; #20 documents the Harness runtime/MCP bridge separately with v0.3.8, GHCR, installation, six-tool scope, and deployment-dependent isolation wording. Review is pending. |
|
Promotion and trust follow-up (2026-08-31): the independent MCP Server Finder evaluation request #4 now includes the merged security hardening PR #117 and targeted verification results. The request remains explicitly open to independent testing; no score or security certification is claimed. |
|
Public discovery update (2026-08-31): four additional external submissions are confirmed merged and publicly visible:
These are independent directory entries, not endorsements or security certifications. |
|
Public discovery update (2026-08-31): Eric-LLMs/Awesome-AI-Engineering PR #4 has merged and now publicly lists SandBase Harness in its agent-engineering project table. The entry covers the local-first runtime, persistent sessions, MCP, sandboxing, approvals, audit, and replay; it is an independent catalog entry, not a certification. |
|
Promotion update (2026-08-31):
Tracking commit: 32bc56b |
|
Promotion update (2026-08-31):
|
Uh oh!
There was an error while loading. Please reload this page.
SandBase Harness is an open-source, local-first agent runtime and MCP bridge for auditable sessions.
For DevOps and platform workflows, the project combines persistent sessions, sandboxed execution, explicit approvals, credential scoping, audit/replay records, and Docker/Kubernetes execution backends. The MCP bridge currently exposes six tools and can be installed from the published v0.3.8 image.
Start here:
Isolation is deployment-dependent: Docker, Kubernetes, and worker backends have different security properties, and the project does not claim universal microVM or kernel isolation. Feedback, deployment reports, and independent review are welcome.
All reactions