SandBase Harness
OCI · GHCR.IO/SANDBASEAI/SANDBASE-HARNESS-MCP:0.3.8
Stdio MCP bridge for SandBase Harness agents, sessions, turns, artifacts, and cancellation.
Available components
Last scanned (9 hours ago)
Scores higher than 98% of OCI servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sandbaseai/sandbase-harness). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 66 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 207 tokens (~34/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_session" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | sandbaseai/sandbase-harness |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sandbaseai/sandbase-harness/.github/workflows/publish-mcp-image.yml@refs/tags/v0.3.8 |
| Rekor log index | 2647573992 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:b86f6ec087a79716535e3b9705b32abe135df6b19bed57fb18914babb273a92b |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_session ~56
Create a SandBase managed-agents session for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent id, for example agent_assistant |
| environment_id | string | – | Optional environment id |
| title | string | – | Optional session title |
No output schema declared.
No examples provided.
get_session ~31
Get the current state and usage of a managed-agents session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session id |
No output schema declared.
No examples provided.
list_agents ~21
List agents available in the connected SandBase managed-agents runtime.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_artifacts ~29
List artifacts produced by a managed-agents session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session id |
No output schema declared.
No examples provided.
run_session ~44
Send a message to a session and wait until its streamed turn becomes idle.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | User message to run |
| session_id | string | yes | Session id |
No output schema declared.
No examples provided.
stop_session ~26
Stop a running managed-agents session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session id |
No output schema declared.
No examples provided.
How do I install the SandBase Harness MCP server?
SandBase Harness runs locally as a container image, launched with docker run --rm -i -e MANAGED_AGENTS_URL -e MANAGED_AGENTS_API_KEY ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8
claude mcp add sandbaseai-sandbase-harness -- docker run --rm -i -e MANAGED_AGENTS_URL -e MANAGED_AGENTS_API_KEY ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8
This image reads MANAGED_AGENTS_URL and MANAGED_AGENTS_API_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the SandBase Harness MCP server?
SandBase Harness is an MCP server listed in the public MCP registry as io.github.sandbaseai/sandbase-harness. Stdio MCP bridge for SandBase Harness agents, sessions, turns, artifacts, and cancellation. This page covers its container image (ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8).
Is the SandBase Harness MCP server safe to use?
SandBase Harness scores 63 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SandBase Harness MCP server expose?
SandBase Harness exposes 6 tools: list_agents, create_session, run_session, get_session, list_artifacts, stop_session. Their descriptions and schemas cost roughly 207 tokens of context every time the server is loaded.
Is the SandBase Harness MCP server still maintained?
SandBase Harness is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SandBase Harness MCP server under?
SandBase Harness declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.