Eclipse Crosslist MCP

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

Publish once, tracked everywhere: registry-native facets plus a mandate-bound listing ledger.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local stdio MCP server from Eclipse Bazaar that presents registry-native facets and a mandate-bound listing ledger for publishing listings once and tracking…

What you can do
  • The input lists no tools, so capabilities can only be inferred from the short registry description.
  • It is described as supporting a publish-once workflow, where a listing is published in one place and tracked everywhere.
  • It mentions registry-native facets and a mandate-bound listing ledger as the mechanism for that tracking.
  • No further detail on specific operations, data sources or outputs is provided.
When to use it
Consider it only if you already work with Eclipse Bazaar listings and want an assistant to help with a publish-once, tracked-everywhere listing workflow. The available material is too thin to judge fit for any other use.
Requirements
Runs as a local process over stdio on a desktop machine; no web executable. No packages, environment variables, headers or authentication are declared, so setup details are unknown and would need to be confirmed with the provider.
Before you install
The description implies publishing and maintaining listings, which likely writes or changes data, but no tools are documented, so the exact actions and their side effects cannot be verified. No credentials are declared, yet a mandate-bound ledger may involve authorization; confirm what it stores and sends before use.

Installation

In SourceWeft

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