Eclipse Ward

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

Guardian veto verdicts + receipts over fixture actions; local/simulator only.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Eclipse Ward returns guardian veto verdicts and receipts for fixture actions, running locally in a simulator-only mode.

What you can do
  • Returns guardian veto verdicts for fixture actions.
  • Produces receipts recording those verdicts.
  • Operates in a local or simulator-only setting rather than against live systems.
  • No tool list, instructions or README is published, so the exact tool names and inputs are unknown.
When to use it
Consider it only if you want to try out or demonstrate a guardian-style veto and receipt flow against simulated fixture actions, for example in a local test or evaluation setup.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not available as a web executable. No packages, environment variables, headers or authentication are declared, so how it is installed and launched is not documented.
Before you install
The registry description states it is local and simulator only, so verdicts and receipts should not be treated as real enforcement or audit evidence. No tool list, instructions or README is available, so its behavior cannot be reviewed before installing.

Installation

In SourceWeft

  1. Open Eclipse Ward 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.1LatestOct 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.