Eclipse Outwatch

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

Independent uptime/SLA witnessing: hash-chained probe receipts, recomputable trust. LOCAL only.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Eclipse Outwatch is a local, desktop-only MCP server for independent uptime and SLA witnessing with hash-chained probe receipts that can be recomputed.

What you can do
  • Provides independent uptime and SLA witnessing for services.
  • Produces hash-chained probe receipts intended to be recomputable and verifiable.
  • Runs entirely locally on the user's machine, with no remote endpoint.
  • No individual tools are documented in the supplied listing, so the exact operations an assistant can call are not described.
When to use it
Consider it when you need an independent, locally held record of whether a service was up and met its SLA, and want receipts that can be recomputed rather than trusting a single provider's dashboard.
Requirements
Runs as a local process over stdio on a desktop machine; it is not available as a web executable. No packages, environment variables, headers or authentication are declared, so installation details are not specified in the listing.
Before you install
The listing declares no credentials, but it also documents no tools, permissions or data handling, so what it probes, where receipts are stored and whether anything leaves the machine cannot be confirmed from the supplied information. Review the project before installing.

Installation

In SourceWeft

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