
Eclipse Duet
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 29, 2026
Dual-control attestation: two distinct agents counter-sign; pair proves attested family diversity.
Overview
Eclipse Duet is a local desktop MCP server for dual-control attestation, where two distinct agents counter-sign so a pair proves attested family diversity.
- What you can do
- The listing names no individual tools, so capabilities are described only at a high level.
- It supports dual-control attestation: two distinct agents counter-sign an action.
- The resulting pair is meant to prove attested family diversity between the two signers.
- No further operations, inputs or outputs are documented in the supplied material.
- When to use it
- Consider it when a workflow needs a second, independent agent to counter-sign something and you want evidence that the two signers belong to different agent families. It is a narrow, single-purpose server, so it only fits setups built around that dual-control pattern.
- Requirements
- Runs as a local process on the user's machine over stdio, desktop only, with no web executable. No packages, environment variables, headers or authentication are declared, so the actual runtime and setup steps are not documented here.
Installation
In SourceWeft
- Open Eclipse Duet 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.0LatestOct 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.