Eclipse Flood Witness

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

Flood evidence, sealed: NFHL determinations as signed, independently recomputable receipts.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that returns NFHL flood determinations as signed, independently recomputable receipts.

What you can do
  • Provides flood evidence from NFHL determinations, returned as sealed receipts.
  • Receipts are described as signed and independently recomputable, so results can be verified rather than taken on trust.
  • No tool list, instructions or README is published, so the exact operations and output format are not documented.
When to use it
Consider it when an assistant needs flood-zone or NFHL determination evidence that can be checked or archived as a verifiable record, for example in property or insurance-related research.
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 setup details are unclear.
Before you install
The server is essentially undocumented: no tools, instructions or README are provided, so its behavior and data sources cannot be reviewed before installing. It is not stated whether determinations are fetched from a third party or how receipts are signed.

Installation

In SourceWeft

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