# verifiable-claim-seed (pypi · verifiable-claim-seed)

Zero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test.

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

## Components

- pypi · `verifiable-claim-seed`: 79/100 (this document), [markdown](https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed.md), [page](https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed)

## Channel facts

- Registry: `pypi`
- Package: `verifiable-claim-seed`
- Version: `1.3.1`
- 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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 197 tokens (~65/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the verifiable-claim-seed MCP server?

verifiable-claim-seed runs locally as a PyPI package, launched with uvx verifiable-claim-seed. 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 elwsls-verifiable-claim-seed -- uvx verifiable-claim-seed
```

### Cursor

```json
{
  "mcpServers": {
    "elwsls-verifiable-claim-seed": {
      "command": "uvx",
      "args": [
        "verifiable-claim-seed"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "elwsls-verifiable-claim-seed": {
      "command": "uvx",
      "args": [
        "verifiable-claim-seed"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add elwsls-verifiable-claim-seed -- uvx verifiable-claim-seed
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "elwsls-verifiable-claim-seed": {
      "type": "local",
      "command": [
        "uvx",
        "verifiable-claim-seed"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add elwsls-verifiable-claim-seed --command uvx --arg verifiable-claim-seed
```

### Hermes

```yaml
mcp_servers:
  elwsls-verifiable-claim-seed:
    command: "uvx"
    args: ["verifiable-claim-seed"]
```

### Netclaw

```json
{
  "McpServers": {
    "elwsls-verifiable-claim-seed": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verifiable-claim-seed"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add elwsls-verifiable-claim-seed -t stdio -c uvx -a verifiable-claim-seed
```

### Other

```json
{
  "mcpServers": {
    "elwsls-verifiable-claim-seed": {
      "command": "uvx",
      "args": [
        "verifiable-claim-seed"
      ]
    }
  }
}
```

## 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-09-19 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-17 (score 63, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-15 (score 77, +1)

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

### 2026-09-13 (score 76, +1)

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

### 2026-09-12 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 60, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-10 (score 74, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-09 (score 74, +1)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (3)

### `self_test` (~29 tokens)

Run the gate self-test: proves the tool works in this environment. Returns passed/exit_code/output.

### `validate` (~71 tokens)

Check a claim's structure and anchor/frozen hashes WITHOUT executing any code. Safe for untrusted claims. Args: claim (claim JSON text) or claim_path (absolute file path).

Input parameters:

- `claim` (string): Claim document as JSON text
- `claim_path` (string): Absolute path to a claim JSON file

### `verify` (~97 tokens)

Full verification of a claim, INCLUDING executing its repro.script as arbitrary code with no sandbox. REQUIRES allow_execution=true; otherwise refused. Only call this on claims you trust. Args: claim or claim_path, allow_execution.

Input parameters:

- `allow_execution` (boolean, required): Must be true; verify is refused without it
- `claim` (string): Claim document as JSON text
- `claim_path` (string): Absolute path to a claim JSON file

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 60
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 70
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 66
- 2026-08-26: 66
- 2026-08-25: 65
- 2026-08-24: 50

## Common questions

### What is the verifiable-claim-seed MCP server?

verifiable-claim-seed is an MCP server listed in the public MCP registry as io.github.elwsls/verifiable-claim-seed. Zero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test. This page covers its PyPI package (verifiable-claim-seed).

### Is the verifiable-claim-seed MCP server safe to use?

verifiable-claim-seed scores 79 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 verifiable-claim-seed MCP server expose?

verifiable-claim-seed exposes 3 tools: self_test, validate, verify. Their descriptions and schemas cost roughly 197 tokens of context every time the server is loaded.

### Is the verifiable-claim-seed MCP server still maintained?

verifiable-claim-seed 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.

## Links

- PyPI project: https://pypi.org/project/verifiable-claim-seed/
- Socket report: https://socket.dev/pypi/package/verifiable-claim-seed
- Repository: https://github.com/elwsls/verifiable-claim-seed
- Changelog RSS feed: https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed.xml
- Changelog JSON feed: https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed.json
- HTML version of this page: https://verifymcp.io/servers/elwsls-verifiable-claim-seed/verifiable-claim-seed