Eclipse Split

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

Pre-agreed revenue splits sealed at spawn, settled on completion records. LOCAL/fixture only.

The publisher's own server: Split (creator affiliate platform)

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server that seals pre-agreed revenue splits at spawn and settles them against completion records, in a local/fixture-only mode.

What you can do
  • Seal pre-agreed revenue splits when a job or record is spawned
  • Settle those splits against completion records
  • Operate in a local, fixture-only mode
  • 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 are experimenting with revenue-split or settlement logic in a local, fixture-based setup and want an assistant to drive it. With no published tools or documentation, most users have no way to judge whether it fits their workflow.
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 launched is not specified.
Before you install
It deals with revenue splits and settlement, so treat any resulting figures as fixture data rather than real financial records. No tools, instructions or README are published, so its behavior and any data it writes cannot be verified before installing.

Installation

In SourceWeft

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

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestOct 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.

Other Split integrations