Eclipse Roll MCP

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

Filing prep + proof: signed deltas vs the registry's own record; proof seals on exact read-back.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local stdio MCP server for filing preparation and proof, comparing signed deltas against the registry's own record and sealing exact read-back.

What you can do
  • Prepare filings and check them before submission.
  • Compare signed deltas against the registry's own record.
  • Apply proof seals on exact read-back of filed data.
  • No tool list, README or instructions are published, so the exact operations are not documented.
When to use it
Consider it when you need an assistant to help prepare a filing and verify that what was recorded matches the registry's own record, with a proof seal on read-back. The sparse documentation makes it hard to judge fit before installing.
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 setup details are undocumented.
Before you install
The description mentions signed deltas and proof seals, which suggests cryptographic signing or verification, but no key handling is documented. Filing-related actions may write or submit data; confirm what it changes before use. No source, README or tool list is available to audit.

Installation

In SourceWeft

  1. Open Eclipse Roll MCP 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.0LatestOct 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.