Eclipse Promptseal

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

Prompt seal chain + Herald approval binding + incident traceability over fixture prompts only.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that provides a prompt seal chain, Herald approval binding and incident traceability, working over fixture prompts only.

What you can do
  • Record and verify a prompt seal chain over fixture prompts
  • Bind approvals through a Herald approval mechanism
  • Trace incidents back through the sealed prompt records
  • Operate only on fixture prompts, not on live or production prompt data
  • No tool list is published, so exact operations must be confirmed with the provider
When to use it
Consider it when you want to experiment with prompt sealing, approval binding and incident traceability in a controlled setting using fixture prompts, for example to evaluate the concept before adopting it.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, with no web executable. No packages, environment variables, headers or authentication are declared, so the actual runtime and setup must be confirmed with the provider.
Before you install
It is limited to fixture prompts, so it is not a way to seal or audit real production prompts. No tools, packages or configuration are documented, so what it actually does and what it can access cannot be verified from the listing.

Installation

In SourceWeft

  1. Open Eclipse Promptseal 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.3LatestOct 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.