Eclipse Burnline

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

Burn-trajectory forecast over sealed fixture mandates: receipted pre-breach verdicts.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Eclipse Burnline is a local desktop MCP server that forecasts burn trajectories over sealed fixture mandates and returns receipted pre-breach verdicts.

What you can do
  • Forecast burn trajectories over sealed fixture mandates.
  • Produce receipted pre-breach verdicts from those forecasts.
  • No tool list, instructions or README is published, so the exact operations and inputs cannot be confirmed from the registry entry.
When to use it
Consider it only if you already know the Eclipse Burnline product and want its burn-trajectory forecasting and pre-breach verdicts available to a desktop assistant. The sparse listing gives little basis for evaluating it otherwise.
Requirements
Runs as a local process on the user's machine over stdio and is desktop only; it is not available as a web executable. No packages, environment variables, headers or authentication are declared, so the actual runtime and any credentials are unknown.
Before you install
The listing declares no authentication, no environment variables and no published tools, instructions or README, so what data it reads or sends cannot be verified. Treat any verdicts it returns as unverified until you confirm the source and behavior yourself.

Installation

In SourceWeft

  1. Open Eclipse Burnline 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.5LatestOct 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.