Eclipse Adproof

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

Fixture claim substantiation gate; pointer proves BOUND, not that it substantiates.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local stdio MCP server described as a "fixture claim substantiation gate" that checks whether a pointer is bound, not whether it substantiates a claim.

What you can do
  • The listing gives no tool list, instructions or README, so its concrete capabilities are not documented.
  • The registry description frames it as a claim substantiation gate for fixtures, where a pointer proves only that something is BOUND, not that it substantiates the claim.
  • Beyond that framing, nothing is stated about what an assistant could call or what output it returns.
When to use it
Only consider it if you specifically need a gate that distinguishes a bound pointer from an actually substantiated claim in fixture data, and you are prepared to evaluate it without documentation.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not web-executable. No packages, environment variables, headers or authentication are declared, so how it is installed or launched is not specified.
Before you install
No tools, instructions, README, package or credentials are documented, so behavior cannot be verified before installing. The description itself warns that a bound pointer does not mean a claim is substantiated; do not treat a positive result as proof of substantiation.

Installation

In SourceWeft

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