Eclipse Settleseal

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

Three-way settlement reconciliation (simulator, fixture records): ledger vs rail vs payout.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local stdio MCP server for three-way settlement reconciliation, comparing ledger, rail and payout records using a simulator and fixture data.

What you can do
  • Reconcile settlement records across three sources: ledger, rail and payout.
  • Run against a built-in simulator and fixture records rather than live payment data.
  • Compare the three record sets to surface settlement discrepancies.
  • No individual tools are documented, so the exact operations are not described.
When to use it
Worth adding when you want an assistant to walk through settlement reconciliation logic or demo three-way matching on sample data, for example to explore or prototype a reconciliation workflow before wiring it to real payment records.
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 runtime it needs is not specified.
Before you install
It works with a simulator and fixture records, so results do not reflect real settlement data and should not be used for actual accounting. No credentials or write access are declared, but the documentation is minimal, so verify what it does before relying on it.

Installation

In SourceWeft

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