Eclipse Cluster MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 26, 2026

Signed images, governed runtimes — the gate runs first: no verified signature and provenance, no

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Eclipse Cluster MCP is a local, desktop-only server that gates workloads on signed images and verified provenance before a governed runtime runs them.

What you can do
  • The listing provides no tool list, instructions or README, so capabilities can only be inferred from a one-line description.
  • That description frames the server as a gate that checks image signatures and provenance before anything runs.
  • It also refers to governed runtimes, suggesting execution is constrained by policy rather than open.
  • No concrete operations, inputs or outputs are documented.
When to use it
Consider it only if you want an assistant to work with a signature-and-provenance gate in front of container or runtime execution, and you are prepared to evaluate it without documentation. For most users the missing tool list, instructions and README make it hard to judge.
Requirements
Runs as a local process on the user's machine over stdio, desktop only. No packages, environment variables, headers or authentication are declared, so the actual runtime prerequisites are undocumented.
Before you install
The listing declares no tools, no README and no instructions, so what it does and what it can change on your machine cannot be verified. It is described as governing runtimes, which implies it may control or restrict execution; review it before granting access.

Installation

In SourceWeft

  1. Open Eclipse Cluster MCP in the dashboard and add it to a workspace.
  2. 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 26, 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.