Eclipse Scamshield

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

First-payment witnessed risk briefing over fixture sources with receipted acknowledgment.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local stdio MCP server that gives an assistant a first-payment risk briefing drawn from fixture sources, with a receipted acknowledgment step.

What you can do
  • Produce a first-payment risk briefing based on fixture (sample) sources
  • Record a receipted acknowledgment of that briefing
  • No tool list is published, so the exact operations are not documented beyond the registry description.
When to use it
Consider it when you want to try a scam-risk briefing flow for a first payment inside an assistant, using sample data rather than live sources. The published description is very thin, so verify what it actually does before relying on it.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, no web executable. No packages, environment variables, headers or authentication are declared, so the install path is unclear from the manifest.
Before you install
The briefing is built on fixture sources, so it is not a live or authoritative risk assessment. The acknowledgment step is recorded as a receipt, which implies a write action. No tools, README or instructions are published, so behavior cannot be reviewed in advance.

Installation

In SourceWeft

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