Eclipse Boomerang

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

Governed returns for agent purchases: sealed receipt+mandate binding. LOCAL/fixture only.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Eclipse Boomerang is a local, desktop-only MCP server for governed returns on agent purchases, binding a sealed receipt to a mandate; described as…

What you can do
  • Provides governed returns for agent purchases, binding a sealed receipt to a mandate.
  • The registry describes it as local and fixture-only, so it appears intended for local testing rather than live commerce.
  • No tools, instructions or README are published, so the specific operations an assistant can call are not documented.
When to use it
Consider it only if you are working on agent-purchase return flows and want a local, fixture-based setup for experimenting with receipt-and-mandate binding. Without published tools or documentation, most users have no clear reason to add 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 undocumented.
Before you install
The server is described as local/fixture only, so it should not be relied on for real purchases or returns. No tools, instructions or README are provided, so its behavior cannot be reviewed before installing; treat any receipt or mandate data it handles as test data.

Installation

In SourceWeft

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