You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary\n- add the official SandBase Harness MCP bridge as a structured registry entry\n- document its six stdio tools, Docker image, runtime URL, and optional API key\n- qualify that execution isolation depends on the selected backend and deployment configuration\n\n## Verification\n- OpenModels MCP Server Registry Validator
==================================================
Validating MCP server registry...
✅ Validation Passed
Validated 209 files successfully.\n- \n\nThe entry is source-backed by the SandBase Harness repository and installation guide. It does not claim a hosted endpoint, universal isolation, endorsement, or security certification.
The entry points to the official repository and the pinned ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8 image.
MANAGED_AGENTS_URL is required; MANAGED_AGENTS_API_KEY is optional when runtime authentication is enabled.
The description explicitly states that execution isolation depends on the selected backend and deployment configuration; no hosted endpoint, universal isolation, endorsement, or security certification is claimed.
hi @liyangbing
The entry validates successfully, the pinned 0.3.8 image is available for both amd64 and arm64, and the six tool definitions match the v0.3.8 source.
There is one install configuration discrepancy to address. The canonical SandBase MCP configuration includes:
--add-host=host.docker.internal:host-gateway
The submitted Docker arguments omit it. Without this mapping, the MCP container may be unable to reach a Harness runtime running on the same Linux host. Please add the argument so the registry configuration matches the official installation.
PR #20 adds the same sandbase-harness entry but contains outdated tool schemas. Once this change is made, I suggest keeping this PR and closing #20 as superseded.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- add the official SandBase Harness MCP bridge as a structured registry entry\n- document its six stdio tools, Docker image, runtime URL, and optional API key\n- qualify that execution isolation depends on the selected backend and deployment configuration\n\n## Verification\n- OpenModels MCP Server Registry Validator
==================================================
Validating MCP server registry...
✅ Validation Passed
Validated 209 files successfully.\n- \n\nThe entry is source-backed by the SandBase Harness repository and installation guide. It does not claim a hosted endpoint, universal isolation, endorsement, or security certification.