Eclipse Safelist

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

Freshness-windowed signed allowlist feed over fixture entries; entries expire unless re-benched.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Eclipse Safelist is a local stdio MCP server that serves a freshness-windowed, signed allowlist feed of fixture entries which expire unless re-benched.

What you can do
  • Expose a signed allowlist feed of fixture entries to the assistant.
  • Apply a freshness window so entries expire unless they are re-benched.
  • No individual tools are documented in the manifest, so the exact operations are not described.
When to use it
Consider it when you need an assistant to consult a signed allowlist whose entries are only valid for a limited time and must be refreshed. The sparse documentation makes it hard to judge fit without inspecting the server yourself.
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 unclear.
Before you install
The description is very thin: no tools, README or instructions are provided, so behavior cannot be verified before installing. Entries expire unless re-benched, so stale data is a real risk. No credentials are declared, but the local process runs with your user's permissions.

Installation

In SourceWeft

  1. Open Eclipse Safelist 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.3LatestOct 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.