Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SandBase Harness

OCI · GHCR.IO/SANDBASEAI/SANDBASE-HARNESS-MCP:0.3.4 · SCANNED AUG 23

Stdio MCP bridge for SandBase Harness agents, sessions, turns, artifacts, and cancellation.

38 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 3 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: 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.

Install

How do I install the SandBase Harness MCP server?

SandBase Harness runs locally as a container image, launched with docker run --rm -i ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4. 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.4

# add to Claude Code
claude mcp add sandbaseai-sandbase-harness -- docker run --rm -i ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4
// .cursor/mcp.json
{
  "mcpServers": {
    "sandbaseai-sandbase-harness": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sandbaseai-sandbase-harness": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sandbaseai-sandbase-harness -- docker run --rm -i ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sandbaseai-sandbase-harness": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  sandbaseai-sandbase-harness:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sandbaseai-sandbase-harness": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "sandbaseai-sandbase-harness": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4"
      ]
    }
  }
}
Changelog

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.

  • 19 Aug 26 38

    First indexed and scored.

Diagnostics

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 23 Aug 2026 · Analysed oci/ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published
MCP tools · 6 exposed · ~207 tokens

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.

Tool Tokens
create_session ~56

Create a SandBase managed-agents session for an agent.

NameTypeReqDescription
agentstringyesAgent id, for example agent_assistant
environment_idstringOptional environment id
titlestringOptional session title

No output schema declared.

No examples provided.

get_session ~31

Get the current state and usage of a managed-agents session.

NameTypeReqDescription
session_idstringyesSession 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.

NameTypeReqDescription
session_idstringyesSession 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.

NameTypeReqDescription
messagestringyesUser message to run
session_idstringyesSession id

No output schema declared.

No examples provided.

stop_session ~26

Stop a running managed-agents session.

NameTypeReqDescription
session_idstringyesSession id

No output schema declared.

No examples provided.

Common questions

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.4).

Is the SandBase Harness MCP server safe to use?

SandBase Harness scores 38 out of 100 on VerifyMCP. 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 23 August 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.