Eclipse Timecapsule

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

Public seal registry over fixture commitments: seal before the window, score at maturity.

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local MCP server that exposes a public seal registry built on fixture commitments, letting an assistant seal entries before a window and score them at…

What you can do
  • Seal registry entries before a defined window closes
  • Score sealed entries once they reach maturity
  • Work with fixture commitments recorded in a public seal registry
  • No tool list, instructions or README is published, so the exact operations are not documented.
When to use it
Consider it only if you already know the Eclipse Timecapsule seal registry and want an assistant to seal or score entries from a local desktop client. With no published tools or documentation, most users have no way to judge whether it fits their workflow.
Requirements
Runs as a local process over stdio on a desktop machine; no web executable. No packages, environment variables, headers or authentication are declared, so the install method and any account needs are unspecified.
Before you install
The registry description mentions sealing and scoring entries, which likely records or changes data in a public registry; confirm what is written and whether it is permanent before use. No credentials are declared, but the provider's site is the only source of further detail.

Installation

In SourceWeft

  1. Open Eclipse Timecapsule 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.4LatestOct 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.