Eclipse Receiptvault

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

Return-deadline vault: deadlines computed once at purchase from fixture sealed merchant terms.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local stdio MCP server that keeps a vault of purchase return deadlines, computed once at purchase from sealed merchant terms.

What you can do
  • The registry lists no tools, so capabilities are known only from its one-line description.
  • It maintains a return-deadline vault for purchases.
  • Deadlines are computed once at purchase time from sealed merchant terms rather than recalculated later.
  • No further operations, queries or exports are documented.
When to use it
Consider it only if you want an assistant to track when purchased items can still be returned, with deadlines fixed at the moment of purchase. The available documentation is too thin to judge fit for anything beyond that.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not available as a web executable. No packages, environment variables, headers or authentication are declared, so setup details are undocumented.
Before you install
No tools, README or instructions are published, so what the server reads, stores or writes cannot be verified before installing. It is a local process with access to your machine; review it yourself before use.

Installation

In SourceWeft

  1. Open Eclipse Receiptvault 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.3LatestOct 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.