verifiable-claim-seed
PYPI · VERIFIABLE-CLAIM-SEED · SCANNED SEP 20
Zero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test.
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 197 tokens (~65/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
pypi · verifiable-claim-seed
claude mcp add elwsls-verifiable-claim-seed -- uvx verifiable-claim-seed
{
"mcpServers": {
"elwsls-verifiable-claim-seed": {
"command": "uvx",
"args": [
"verifiable-claim-seed"
]
}
}
} {
"servers": {
"elwsls-verifiable-claim-seed": {
"command": "uvx",
"args": [
"verifiable-claim-seed"
]
}
}
} codex mcp add elwsls-verifiable-claim-seed -- uvx verifiable-claim-seed
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"elwsls-verifiable-claim-seed": {
"type": "local",
"command": [
"uvx",
"verifiable-claim-seed"
],
"enabled": true
}
}
} openclaw mcp add elwsls-verifiable-claim-seed --command uvx --arg verifiable-claim-seed
mcp_servers:
elwsls-verifiable-claim-seed:
command: "uvx"
args: ["verifiable-claim-seed"] {
"McpServers": {
"elwsls-verifiable-claim-seed": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"verifiable-claim-seed"
]
}
}
} assistant mcp add elwsls-verifiable-claim-seed -t stdio -c uvx -a verifiable-claim-seed
{
"mcpServers": {
"elwsls-verifiable-claim-seed": {
"command": "uvx",
"args": [
"verifiable-claim-seed"
]
}
}
} 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.
- 19 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 10 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
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/verifiable-claim-seed@1.3.1
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
self_test ~29
Run the gate self-test: proves the tool works in this environment. Returns passed/exit_code/output.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate ~71
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).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | Claim document as JSON text |
| claim_path | string | – | Absolute path to a claim JSON file |
No output schema declared.
No examples provided.
verify ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_execution | boolean | yes | 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 |
No output schema declared.
No examples provided.
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.