SandBase Harness runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 Oct 2026.
Stdio MCP bridge for SandBase Harness agents, sessions, turns, artifacts, and cancellation.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(execPath, argv.slice(1), {
return readdir(safePath(root, stringPayload(item.payload.path ?? '.', 'path')));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to SandBase Harness
same job, measured the same wayThe trust harness for AI agents. Set what an agent can do before it acts.
HYTHE — coordination bus + shared truth for AI agent fleets — self-hosted MCP server + stdio bridge.
Self-hosted MCP server: a case file for every task, shared across sessions, agents and people.
Cross-harness communication and shared work-state for AI coding agents.
DeFi execution for AI agents — swap, lend, bridge, and yield across 22 chains.
Zenrows MCP server: Fetch, Extract, Batch, and Browser Sessions for AI agents
Verified knowledge base for AI agents — stop hallucinations with certified facts.
ElevenLabs Conversational AI: agents, calls, conversations, and knowledge base for MCP hosts
SandBase Harness — questions
Answers built from our own checks of this server.