Eclipse Steward MCP

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

Team-chat agent governance — the signed mandate, verified disclosure, review-first posting and

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Eclipse Steward MCP is a local, desktop-only server for team-chat agent governance, covering signed mandates, verified disclosure and review-first posting.

What you can do
  • The registry entry describes team-chat agent governance: signed mandates, verified disclosure, and review-first posting.
  • No tool list, instructions or README were supplied, so the specific actions an assistant can take are not documented here.
  • The description is cut off mid-sentence, so the full scope of governance features is unclear.
When to use it
Consider it only if you want an assistant's activity in team chat to be governed by signed mandates, disclosure checks and a review step before messages are posted. Because no tools or documentation are published, confirm its behaviour with the provider 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, authentication, environment variables or headers are declared, so setup details are not documented.
Before you install
The server is described as posting to team chat, so expect it to send messages on your behalf; the review-first step should be kept in place. No credentials are declared, but the signed-mandate and disclosure features imply identity or signing material whose handling is undocumented. Verify what it stores and sends before installing.

Installation

In SourceWeft

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