Eclipse Morphguard

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

Fixture payee drift evidence; pinned fixture keys, not public keys; export packs not value-free.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local stdio MCP server, Eclipse Morphguard, described only as producing fixture payee drift evidence with pinned fixture keys.

What you can do
  • The registry entry lists no tools, so the assistant-facing capabilities cannot be determined from the supplied material.
  • The description mentions producing fixture payee drift evidence.
  • It states that the keys involved are pinned fixture keys rather than public keys.
  • It notes that export packs are not value-free.
When to use it
Only consider it if you specifically need fixture payee drift evidence in a local, desktop-only setup and are prepared to evaluate it without documentation, since no tools, instructions or README are provided.
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 the actual runtime requirements are unknown.
Before you install
The description says export packs are not value-free, so exported data may contain sensitive values. The keys used are pinned fixture keys, not public keys, so do not treat them as production or public key material. With no tools, instructions or README available, behavior cannot be verified before installing.

Installation

In SourceWeft

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