
Eclipse Scapegoat
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.2Updated Oct 29, 2026
Failure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Overview
Local stdio MCP server that recomputes failure attribution over hash-chained fixture records and returns a verdict with a proof path.
- What you can do
- Recompute failure attribution over hash-chained fixture records.
- Return a verdict together with a proof path for the recomputation.
- Operate entirely locally, on the user's own machine.
- When to use it
- Worth considering when you need to re-derive who or what a failure should be attributed to from hash-chained fixture records, and want a verifiable proof path rather than a bare conclusion. It is a narrow, local-only utility, so it only helps if your data is already in that fixture format.
- Requirements
- Runs as a local process over stdio on a desktop machine; no web executable is offered. No packages, environment variables, headers or authentication are declared, so the runtime and how the fixture records are supplied are not specified in the available information.
Installation
In SourceWeft
- Open Eclipse Scapegoat in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.2LatestOct 29, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.