Eclipse Skillseal

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

Machine-checkable skill claims over fixture claims + receipts; no receipt renders UNVERIFIED.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that lets an assistant make machine-checkable skill claims backed by fixture claims and receipts, marking anything without a receipt as…

What you can do
  • The manifest lists no tools, so capabilities come from the short registry description.
  • It appears to let an assistant submit skill claims that are checked against fixture claims and receipts.
  • Claims lacking a receipt are reported as UNVERIFIED rather than accepted.
  • The result is a machine-checkable verdict on whether a claimed skill is backed by evidence.
When to use it
Worth considering when you want an assistant's statements about skills or capabilities to be gated on verifiable receipts, and you need unbacked claims clearly flagged as unverified.
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 in the supplied material.
Before you install
The description is very terse and no tools, README or instructions are provided, so the exact behavior and data handling cannot be confirmed before installing. Verify what it reads and writes locally, and treat UNVERIFIED results as a signal that evidence is missing rather than proof of correctness.

Installation

In SourceWeft

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