Eclipse Phantom

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

Phantom-charge sentinel over fixture charges + mandates; assembles dispute packs, transmits nothing.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local stdio MCP server that watches fixture charges and mandates and assembles dispute packs, without transmitting anything.

What you can do
  • Monitors fixture charges and mandates as a "phantom-charge" sentinel.
  • Assembles dispute packs from those records.
  • Transmits nothing: output stays local for review.
  • No tool list, README or instructions are published, so the exact operations are undocumented.
When to use it
Consider it only if you work with charge and mandate dispute handling and want an assistant to assemble draft dispute packs locally for review. Because no tools or documentation are published, verify its behavior before relying on it.
Requirements
Runs as a local process over stdio on a desktop machine; no web executable. No packages, authentication, environment variables or headers are declared, so setup details are undocumented.
Before you install
The description mentions charges, mandates and disputes, which are financially sensitive records; confirm what data it reads and where output goes. Nothing is declared about credentials or network access, and no tool list is published, so review it before installing.

Installation

In SourceWeft

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