Eclipse Regulens

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

Regulation-change impact receipts mapped to declared controls. Not legal advice.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Eclipse Regulens maps regulation changes to declared controls and produces impact receipts; it is a local desktop-only MCP server, not legal advice.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the description only.
  • Map regulation changes to controls the user has declared.
  • Produce impact receipts recording how a change affects those controls.
  • It is positioned as a compliance aid rather than a source of legal advice.
When to use it
Consider it when you track regulatory changes and want an assistant to connect each change to the controls you have declared and record the impact. It is not a substitute for legal review.
Requirements
Runs as a local process over stdio on the user's desktop; no packages, environment variables, headers or authentication are declared, so setup details are not documented in the listing.
Before you install
The server states it is not legal advice, so its output should be reviewed by a qualified person before being relied on. No tools, credentials or data flows are documented, so what it reads, writes or sends elsewhere cannot be verified from the listing.

Installation

In SourceWeft

  1. Open Eclipse Regulens 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.2LatestOct 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.