# io.github.sandbaseai/sandbase-harness

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.3.8
- **Author:** io.github.sandbaseai
- **License:** Unknown
- **Source:** https://github.com/sandbaseai/sandbase-harness

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-02T00:08:53.125Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

13 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_agents` — List agents available in the connected SandBase managed-agents runtime.
- `create_session` — Create a SandBase managed-agents session for an agent.
- `run_session` — Send a message to a session and wait until its streamed turn becomes idle.
- `get_session` — Get the current state and usage of a managed-agents session.
- `list_artifacts` — List artifacts produced by a managed-agents session.
- `stop_session` — Stop a running managed-agents session.
- `echo` — Echo back the provided text
- `runtime-agent` — Created through the API.
- `docker`
- `my-template` — test
- `valid-template` — test
- `one` — first
- `two` — second

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no package coordinates and no declared endpoint — Forge cannot tell where this would run or whose authority it would borrow. Known so far: holds an api key; read-only tool surface.
- Floor 13, ceiling 25 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.sandbaseai%2Fsandbase-harness
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.sandbaseai%2Fsandbase-harness/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.sandbaseai%2Fsandbase-harness
- HTML page: https://forgeregistry.com/registry/io.github.sandbaseai%2Fsandbase-harness
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.