Eclipse Ledger MCP

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

Eclipse Ledger — betting records, price comparison, and responsible-gambling controls. Not a

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Eclipse Ledger is a local MCP server for betting records, price comparison and responsible-gambling controls, though its description is cut off.

What you can do
  • The registry description is truncated and no tools, instructions or README are provided, so the exact tool set is unknown.
  • Based on the description, it is meant to keep betting records, compare prices and apply responsible-gambling controls.
  • No further capabilities can be confirmed from the supplied material.
When to use it
Consider it only if you want an assistant to help track betting activity, compare odds or prices, and apply responsible-gambling limits; verify the actual tools before relying on it.
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 setup details are unclear.
Before you install
The description is incomplete, so what the server actually does cannot be fully verified. It concerns betting and gambling records, which may involve money and personal financial data; review the source before installing.

Installation

In SourceWeft

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

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 26, 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.