Eclipse Corona MCP

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

Sealed render-proof for deployed websites — signed verdicts bound to the deployed artifact.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that provides sealed, signed render-proof verdicts for deployed websites, bound to the deployed artifact.

What you can do
  • Produces signed render-proof verdicts for deployed websites.
  • Binds each verdict to the specific deployed artifact it was checked against.
  • Runs as a local process on the user's desktop machine.
  • No tool list, instructions or README is published, so the exact operations an assistant can call are not documented.
When to use it
Consider it when you need verifiable evidence that a deployed website renders as expected, and want a signed verdict tied to the exact deployed artifact rather than an informal screenshot check.
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 not documented.
Before you install
The server publishes no tool list, instructions or README, so what it reads, sends or writes cannot be verified before installing. It is desktop-only and not available as a web executable. No credentials are declared, but confirm what data leaves your machine.

Installation

In SourceWeft

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

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.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.