
Eclipse Ancestor
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.2Updated Oct 29, 2026
Sealed model-ancestry chains + buyer policy checks; declared-and-sealed, local only.
Overview
Eclipse Ancestor is a local, desktop-only MCP server that provides sealed model-ancestry chains and buyer policy checks.
- What you can do
- Provides sealed model-ancestry chains, per the registry description.
- Performs buyer policy checks against those chains.
- Runs entirely locally as a declared-and-sealed process on the user's machine.
- No tool list, README or instructions are published, so the exact operations available to an assistant are not documented.
- When to use it
- Consider it when you need to trace or verify the ancestry of a model and apply buyer-side policy checks locally, without sending that data to a remote service. Because no tools or documentation are published, confirm its behavior before relying on it.
- Requirements
- Runs as a local process over stdio on a desktop machine; no web executable. No packages, environment variables, headers or authentication are declared, so the runtime and installation method are not specified in the listing.
Installation
In SourceWeft
- Open Eclipse Ancestor 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.