
Eclipse Exportcheck
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.7Updated Oct 29, 2026
Vintage-sealed fixture screening verdicts; clearance provable after lists change, local.
Overview
Local stdio MCP server that returns screening verdicts for vintage-sealed fixtures, with clearance provable after lists change.
- What you can do
- Provides screening verdicts for vintage-sealed fixtures.
- Reports whether a fixture clears screening, with clearance that stays provable after the underlying lists change.
- Runs entirely locally on the user's machine over stdio.
- No tool list, instructions or README is published, so the exact operations are not documented.
- When to use it
- Consider it when you need local, repeatable screening verdicts on vintage-sealed fixtures and want clearance results that remain verifiable after reference lists are updated. It is a narrow, single-purpose tool; most users will not need it.
- 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 requirement is undocumented.
Installation
In SourceWeft
- Open Eclipse Exportcheck 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.7LatestOct 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.