Eclipse Scapegoat
Recompute failure attribution over hash-chained fixture records, returning a verdict
- Platforms
- self-hosted
- Version
- 0.1.2
- Listing updated
- today
Similar MCP servers
About Eclipse Scapegoat
Eclipse Scapegoat is an MCP server for agent tooling. It is available on self-hosted.
Eclipse Scapegoat is a local-only MCP server from Cyan Eclipse Technologies. According to its registry entry, it recomputes failure attribution over hash-chained fixture records and returns a verdict together with a proof path showing how that verdict was reached.
It appears to belong to the Cyan Eclipse family of governed, evidence-oriented agent tools, which are listed on the Cyan Eclipse Bazaar. That marketplace benches tools on its Verity Bench and publishes scoped scorecards. The excerpt of the Bazaar catalog available here does not show a certification verdict or tool list for Scapegoat itself.
The registry entry declares no transports, packages or remote endpoints, so it is meant to be run from the source repository rather than connected to as a hosted service. It suits developers who want to examine how blame can be traced back through tamper-evident records.
What it does
- Failure attribution recompute
- Recomputes which step or party is responsible for a failure rather than relying on a stored conclusion.
- Hash-chained records
- Works over hash-chained fixture records, so the input history is tamper-evident.
- Verdict with proof path
- Returns both an attribution verdict and the proof path that supports it.
- Local-only operation
- Runs locally against fixture data and does not expose a remote endpoint.
Good for
- Tracing a failed agent run back to the responsible step using fixture records
- Checking that an attribution verdict can be reproduced from a hash chain
- Testing failure-analysis logic against fixture data before using real records
- Auditing how blame is assigned in multi-step agent workflows
Eclipse Scapegoat FAQ
Does Eclipse Scapegoat run remotely?
No. The registry entry describes it as local only and lists no remote endpoints or packages.
What does it return?
A verdict on failure attribution plus the proof path behind it.
What data does it operate on?
Hash-chained fixture records.
Who publishes it?
Cyan Eclipse Technologies LLC, with source in a GitHub repository under that organization.
What are the best alternatives to Eclipse Scapegoat?
The closest alternatives to Eclipse Scapegoat are Eclipse Capline, Eclipse Epitaph, Eclipse Fairlend, Eclipse Ward and Eclipse Burnline.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.