Eclipse Blackbox MCP

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

The record that survives the agent: append-only, recorder-signed, and graded by proof — never by

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local stdio MCP server called Eclipse Blackbox that presents itself as an append-only, recorder-signed record graded by proof.

What you can do
  • The listing gives no tool list, instructions or README, so the concrete capabilities are not documented.
  • The registry description frames it as an append-only record that survives the agent, signed by a recorder and graded by proof rather than by assertion.
  • Beyond that framing, nothing in the supplied material shows what an assistant can actually read, write or query.
When to use it
Only consider it if you specifically want a tamper-evident, signed record of agent activity and are willing to evaluate it without documentation. Most users should wait for a published tool list and README before installing.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not available as a web executable. No packages, environment variables, headers or authentication are declared, so the actual runtime and setup requirements are unknown.
Before you install
No tools, permissions or data handling are documented, so what it records, where that data goes and whether it writes or signs anything cannot be verified. Treat the append-only, signed-record claims as unverified marketing until you can inspect the code or documentation.

Installation

In SourceWeft

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