io.github.spec-family/spec-harness
spec-harness
Is the spec-harness MCP server down? Yes. It has given no valid answer since 2026-11-12: crashed on start.
Rounds of agent work under a brief: context to start, a check on each path, an audit at the end.
crashed on start down since 2026-11-12 · probed 2026-11-15 · unchanged since 2026-11-14
MCP error -32000: Connection closed spec-harness: /work is not inside a git work tree; spec-harness measures rounds by their commits
- Run it
- npx -y @spec-family/spec-harness@0.26.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/spec-family/spec-harness
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.spacecowboyian/brains · needs env
- io.github.spacepacket1/e3d-pilot · crashed on start
- io.github.spanlens/mcp-server · needs network
- spec-guard io.github.spec-family/spec-guard · alive
- io.github.specshield-io/specshield-mcp-server · alive
- io.github.specshield26/specshield-mcp-server · alive
- io.github.spectra-g/engram · alive
- SpeechWeave io.github.speechweave/mcp · alive
Servers that mention harness.
- Bring Your AI ai.bringyour/bringyour · alive
- SignalHarness.ai ai.signalharness/mcp · server error
- Webhound ai.webhound/webhound · needs auth
- com.clauxel.clianythingharness/clianythingharness-mcp · no DNS
- com.clauxel.jcodeharness/jcodeharness-mcp · no DNS
- SuperSkill Registry com.onlyharness/registry · alive
- Santismm Knowledge — Harness Engineering, Agentic AI & Governance com.santismm/knowledge · alive
- Agent Reliability dev.agentreliability/agent-reliability · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-12, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.