com.olane/copass-local
PYPI · OLANE-COPASS-LOCAL · SCANNED SEP 20
Local encryption and project setup plugin for Copass. Keys never leave your machine.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 198 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 734 tokens (~122/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.olane/copass-local MCP server?
com.olane/copass-local runs locally as a PyPI package, launched with uvx olane-copass-local. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · olane-copass-local
claude mcp add com-olane-copass-local -- uvx olane-copass-local
{
"mcpServers": {
"com-olane-copass-local": {
"command": "uvx",
"args": [
"olane-copass-local"
]
}
}
} {
"servers": {
"com-olane-copass-local": {
"command": "uvx",
"args": [
"olane-copass-local"
]
}
}
} codex mcp add com-olane-copass-local -- uvx olane-copass-local
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-olane-copass-local": {
"type": "local",
"command": [
"uvx",
"olane-copass-local"
],
"enabled": true
}
}
} openclaw mcp add com-olane-copass-local --command uvx --arg olane-copass-local
mcp_servers:
com-olane-copass-local:
command: "uvx"
args: ["olane-copass-local"] {
"McpServers": {
"com-olane-copass-local": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"olane-copass-local"
]
}
}
} assistant mcp add com-olane-copass-local -t stdio -c uvx -a olane-copass-local
{
"mcpServers": {
"com-olane-copass-local": {
"command": "uvx",
"args": [
"olane-copass-local"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/olane-copass-local@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
encrypt_file Encrypt File ~76
Encrypt a file's contents with AES-256-GCM. Reads the file, encrypts its contents, writes the encrypted data to a temporary file, and returns the path along with IV and tag. The master key is loaded automatically — no need to provide it.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to encrypt |
Structured output declared, but exposes no named fields.
No examples provided.
encrypt_payload Encrypt Payload ~67
Encrypt a text payload with AES-256-GCM. Returns base64-encoded encrypted fields suitable for passing to copass MCP server's ingest_text or ingest_code tools. The master key is loaded automatically — no need to provide it.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Plaintext to encrypt |
Structured output declared, but exposes no named fields.
No examples provided.
generate_session_token Generate Session Token ~77
Generate a session token by wrapping the DEK with the access token. Call this at session start. The returned token is opaque and should be passed to the copass MCP server via the encryption_token parameter. The master key is loaded automatically — no need to provide it.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | Supabase JWT access token |
Structured output declared, but exposes no named fields.
No examples provided.
set_copass_encryption_key Set Copass Encryption Key ~87
Write a user-provided master key to .olane/config.json. Use this for migration or team key sharing — overwrites any existing key. Not needed for normal operation (keys are auto-provisioned).
| Name | Type | Req | Description |
|---|---|---|---|
| copass_encryption_key | string | yes | The master key string to store |
| project_path | string | yes | Absolute path to the project root directory |
Structured output declared, but exposes no named fields.
No examples provided.
setup_project Setup Project ~145
Write all copass setup files to a project directory. Creates hooks, scripts, .olane/config.json, and merges settings into .claude/settings.local.json. Strips any legacy copass section from CLAUDE.md.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_type | string | yes | Type of coding agent (e.g. "claude_code") |
| api_url | string | – | Optional API URL (defaults to OLANE_API_URL env or http://localhost:8000) |
| auth_token | string | – | Optional OAuth access token to store in config |
| project_path | string | yes | Absolute path to the project root directory |
| user_id | string | yes | Authenticated user ID |
Structured output declared, but exposes no named fields.
No examples provided.
update_auth_token Update Auth Token ~88
Update the auth_token in .olane/config.json without exposing it to the user. Called during session initialization after check_project_status returns a fresh token. This avoids the Claude Code Edit/Write permission prompt which would display the token to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | string | yes | Fresh access token to persist |
| project_path | string | yes | Absolute path to the project root directory |
Structured output declared, but exposes no named fields.
No examples provided.
What is the com.olane/copass-local MCP server?
com.olane/copass-local is an MCP server listed in the public MCP registry as com.olane/copass-local. Local encryption and project setup plugin for Copass. Keys never leave your machine. This page covers its PyPI package (olane-copass-local).
Is the com.olane/copass-local MCP server safe to use?
com.olane/copass-local scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.olane/copass-local MCP server expose?
com.olane/copass-local exposes 6 tools: generate_session_token, encrypt_payload, encrypt_file, update_auth_token, setup_project, set_copass_encryption_key. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.
Is the com.olane/copass-local MCP server still maintained?
com.olane/copass-local is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.