Eclipse Thread MCP

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

On-prem bridges for the legacy software-engineering toolchain, plus the Evidence Weaver that joins

The publisher's own server: ThreadPage

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server offering on-prem bridges to a legacy software-engineering toolchain, plus an "Evidence Weaver" that joins results.

What you can do
  • The listing names no tools, so capabilities come only from the short description.
  • It presents itself as on-prem bridges into a legacy software-engineering toolchain.
  • It also mentions an "Evidence Weaver" that joins something together, but the description is cut off and does not say what is joined or how.
  • No further detail on commands, inputs or outputs is available.
When to use it
Only worth considering if you already work with the legacy software-engineering toolchain it targets and want an assistant to reach it from a desktop client. Because the description is truncated and no tools are documented, confirm what it actually exposes before relying on it.
Requirements
Runs as a local process on the user's machine over stdio, desktop clients only. No packages, environment variables, headers or authentication are declared, so the runtime and any prerequisites are undocumented.
Before you install
The description is truncated and no tools, README or instructions are provided, so what the server can read or change is unknown. It is described as on-prem, which suggests it may reach internal systems; review its behavior before granting access to sensitive repositories or data.

Installation

In SourceWeft

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

Other Thread integrations