Eclipse Verbatim — Executive Orders

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

Executive Orders, sealed: per-section hashes plus a provenance-typed disposition graph.

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local MCP server that serves sealed Executive Orders data, with per-section hashes and a provenance-typed disposition graph.

What you can do
  • The listing names no tools, so capabilities can only be inferred from the description.
  • It is described as providing Executive Orders content in a sealed form, with per-section hashes.
  • It also exposes a disposition graph whose edges carry provenance types.
  • No further detail on queries, sections or output formats is given.
When to use it
Consider it only if you need an assistant to work with Executive Orders text where per-section integrity hashes and provenance-typed dispositions matter. The sparse listing gives little basis for judging fit, so verify behavior before relying on it.
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 data source are unspecified.
Before you install
The listing declares no tools, README or instructions, so what the server reads, writes or sends elsewhere cannot be verified. Treat the sealed hashes and provenance graph as unverified claims until you inspect the process yourself.

Installation

In SourceWeft

  1. Open Eclipse Verbatim — Executive Orders 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.