Copass Local

com.olanePublished by olane.comv0.3.2Updated Oct 24, 2026

Local encryption and project setup plugin for Copass. Keys never leave your machine.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Copass Local is a local plugin for Copass that handles encryption and project setup, keeping keys on the user's own machine.

What you can do
Provides local encryption and project setup for Copass projects, running as a plugin on the user's machine rather than as a hosted service. The registry description states that keys never leave the machine, so key handling stays local. No tool list, instructions or README are provided, so the exact operations the assistant can invoke are not documented here.
When to use it
Worth considering if you already use Copass and want its encryption and project setup handled locally, with keys kept on your own machine. Not enough detail is published to recommend it for other uses.
Requirements
Runs as a local process on the user's machine via the PyPI package olane-copass-local over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The server handles encryption keys, so review how it stores and uses them before installing. No tool list or documentation is published, so what it can read, write or change is unclear. It is desktop-only and cannot be used from a web client.

Installation

In SourceWeft

  1. Open Copass Local 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.3.2LatestSep 16, 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.