Eclipse Ballotbox

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

Ballots sealed to vote-time mandate-eligibility proofs; fixture elections, local only.

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local, desktop-only MCP server for fixture elections where ballots are sealed to vote-time mandate-eligibility proofs.

What you can do
  • Works with fixture elections that run entirely on the local machine.
  • Seals ballots so they are bound to vote-time mandate-eligibility proofs.
  • No tool list, instructions or README is published, so the exact operations an assistant can call are not documented.
When to use it
Only worth considering if you are experimenting with local, fixture-only election or ballot-sealing concepts and want an assistant to drive them. Because no tools or documentation are published, most users have no way to judge whether it fits their needs.
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 how it is installed and launched is not specified.
Before you install
The server is described as fixture and local-only, so it should not be treated as a real election or voting system. No tool list, instructions or README is available, so its behavior and any data it writes cannot be verified before installing.

Installation

In SourceWeft

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