Eclipse Feeseal

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

Fee-schedule sealing + fee verification over fixture transactions; detection only, never charges.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server that seals fee schedules and verifies fees against fixture transactions, reporting detection results without ever charging.

What you can do
  • Seal fee schedules and verify fees against fixture transactions.
  • Report detection results for fee mismatches, with no charging or payment actions performed.
  • The manifest lists no individual tools, so the exact operations are not documented; the description covers only sealing and verification over fixtures.
When to use it
Worth considering when you want an assistant to check fee calculations against sample or fixture transaction data and confirm a fee schedule is sealed, in a detection-only setting where nothing is billed.
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 setup details are not documented.
Before you install
The server is described as detection only and never charges, but the manifest declares no authentication and no tool list, so review what it does before pointing it at real fee or transaction data. Fixture data handling and any third-party transmission are not documented.

Installation

In SourceWeft

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