Eclipse Epitaph

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

Signed death record triggers atomic cascade expiry of fixture instruments; local only.

VerifiedSTDIODesktop only

Overview

AI-generated overview

Local-only MCP server that triggers atomic cascade expiry of fixture instruments from a signed death record.

What you can do
  • Triggers atomic cascade expiry of fixture instruments based on a signed death record.
  • Works locally on the user's machine over stdio, with no remote endpoint.
  • No tool list, instructions or README is published, so the exact operations an assistant can call are not documented.
When to use it
Consider it only if you already know the Eclipse Epitaph workflow and need an assistant to drive cascade expiry of fixture instruments from a signed death record on your own machine. Most users will find too little public documentation to evaluate it.
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 run is not specified.
Before you install
The server acts on signed death records and expires fixture instruments, which is a destructive, irreversible change; confirm what it will expire before letting an assistant call it. No tool list, instructions or README is published, so its behavior cannot be reviewed in advance. It is local-only and declares no credentials.

Installation

In SourceWeft

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