# Keystash (pypi · keystash)

Keychain-backed secret broker: an AI agent can use your keys, but no tool ever returns one.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `keystash`: 65/100 (this document), [markdown](https://verifymcp.io/servers/thu-lawyer-keystash/keystash.md), [page](https://verifymcp.io/servers/thu-lawyer-keystash/keystash)

## Channel facts

- Registry: `pypi`
- Package: `keystash`
- Version: `0.4.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 3 of 12 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to thu-lawyer/keystash).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 490 tokens (~81/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "secret_use" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Keystash MCP server?

Keystash runs locally as a PyPI package, launched with uvx keystash. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add thu-lawyer-keystash -- uvx keystash
```

### Cursor

```json
{
  "mcpServers": {
    "thu-lawyer-keystash": {
      "command": "uvx",
      "args": [
        "keystash"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thu-lawyer-keystash": {
      "command": "uvx",
      "args": [
        "keystash"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add thu-lawyer-keystash -- uvx keystash
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thu-lawyer-keystash": {
      "type": "local",
      "command": [
        "uvx",
        "keystash"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thu-lawyer-keystash --command uvx --arg keystash
```

### Hermes

```yaml
mcp_servers:
  thu-lawyer-keystash:
    command: "uvx"
    args: ["keystash"]
```

### Netclaw

```json
{
  "McpServers": {
    "thu-lawyer-keystash": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "keystash"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add thu-lawyer-keystash -t stdio -c uvx -a keystash
```

### Other

```json
{
  "mcpServers": {
    "thu-lawyer-keystash": {
      "command": "uvx",
      "args": [
        "keystash"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-04 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 64, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 78, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `secret_list` (~57 tokens)

List stored secrets as metadata only: name, tags, rotation policy, last rotation, allowed URLs. Never returns a value.

Input parameters:

- `name` (string): Return only this entry.
- `tag` (string): Return only entries carrying this tag.

### `secret_store` (~136 tokens)

Store a secret. The value is collected from the human through a native macOS dialog; it is never passed as an argument and never returned. Use this only when the human is present.

Input parameters:

- `allowed_urls` (array): URL prefixes this entry may be sent to, each ending with '/'. secret_use refuses every other destination.
- `auth_header` (string): Default 'Authorization'.
- `auth_prefix` (string): Default 'Bearer '.
- `name` (string, required): Reference name, SERVICE_ENV_PURPOSE, e.g. OPENAI_PROD_KEY.
- `rotate_every_days` (integer)
- `tags` (array)

### `secret_rotate` (~66 tokens)

Replace an existing secret's value with a new one collected from the human through a native macOS dialog. Metadata is preserved unless overridden.

Input parameters:

- `allowed_urls` (array)
- `name` (string, required)
- `rotate_every_days` (integer)
- `tags` (array)

### `secret_generate` (~88 tokens)

Generate a high-entropy value, store it, and return only a short fingerprint. The value is never returned; the human retrieves it with `keystash copy NAME` (clipboard, auto-cleared).

Input parameters:

- `allowed_urls` (array)
- `length` (integer)
- `name` (string, required)
- `rotate_every_days` (integer)
- `tags` (array)

### `secret_use` (~106 tokens)

Send one HTTP request to an allow-listed URL with the entry's value as its credential. Returns the status and the scrubbed response body. The AI does not choose the credential and cannot read it.

Input parameters:

- `body`: Request body: object, string, or omitted.
- `method` (string): Default GET.
- `name` (string, required)
- `timeout` (number): Seconds, max 300.
- `url` (string, required): Must be covered by the entry's allowed_urls.

### `secret_delete` (~37 tokens)

Delete a secret and its metadata. Requires a native confirmation dialog from the human; without it nothing is deleted.

Input parameters:

- `name` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/thu-lawyer-keystash/keystash#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 80
- 2026-11-03: 64
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 62
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 60
- 2026-10-24: 60
- 2026-10-23: 59
- 2026-10-22: 59
- 2026-10-21: 63
- 2026-10-20: 60
- 2026-10-19: 60
- 2026-10-18: 75
- 2026-10-17: 60
- 2026-10-16: 60
- 2026-10-15: 60
- 2026-10-14: 60
- 2026-10-13: 34
- 2026-10-12: 49

## Common questions

### What is the Keystash MCP server?

Keystash is an MCP server listed in the public MCP registry as io.github.thu-lawyer/keystash. Keychain-backed secret broker: an AI agent can use your keys, but no tool ever returns one. This page covers its PyPI package (keystash).

### Is the Keystash MCP server safe to use?

Keystash scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Keystash MCP server expose?

Keystash exposes 6 tools: secret_list, secret_store, secret_rotate, secret_generate, secret_use, secret_delete. Their descriptions and schemas cost roughly 490 tokens of context every time the server is loaded.

### Is the Keystash MCP server still maintained?

Keystash is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Keystash MCP server under?

Keystash declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/keystash/
- Socket report: https://socket.dev/pypi/package/keystash
- Website: https://pypi.org/project/keystash/
- Changelog RSS feed: https://verifymcp.io/servers/thu-lawyer-keystash/keystash.xml
- Changelog JSON feed: https://verifymcp.io/servers/thu-lawyer-keystash/keystash.json
- HTML version of this page: https://verifymcp.io/servers/thu-lawyer-keystash/keystash