com.pcrzero/mcp
NPM · @SCYTALEX-LLC/PCRZERO-MCP · 2 COMPONENTS · SCANNED OCT 3
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 491 tokens (~163/item across 3 items; 3 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.pcrzero/mcp server?
com.pcrzero/mcp runs locally as an npm package, launched with npx -y @scytalex-llc/pcrzero-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @scytalex-llc/pcrzero-mcp
claude mcp add com-pcrzero-mcp -- npx -y @scytalex-llc/pcrzero-mcp
{
"mcpServers": {
"com-pcrzero-mcp": {
"command": "npx",
"args": [
"-y",
"@scytalex-llc/pcrzero-mcp"
]
}
}
} {
"servers": {
"com-pcrzero-mcp": {
"command": "npx",
"args": [
"-y",
"@scytalex-llc/pcrzero-mcp"
]
}
}
} codex mcp add com-pcrzero-mcp -- npx -y @scytalex-llc/pcrzero-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pcrzero-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@scytalex-llc/pcrzero-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-pcrzero-mcp --command npx --arg -y --arg @scytalex-llc/pcrzero-mcp
mcp_servers:
com-pcrzero-mcp:
command: "npx"
args: ["-y", "@scytalex-llc/pcrzero-mcp"] {
"McpServers": {
"com-pcrzero-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@scytalex-llc/pcrzero-mcp"
]
}
}
} assistant mcp add com-pcrzero-mcp -t stdio -c npx -a -y @scytalex-llc/pcrzero-mcp
{
"mcpServers": {
"com-pcrzero-mcp": {
"command": "npx",
"args": [
"-y",
"@scytalex-llc/pcrzero-mcp"
]
}
}
} 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.
- 2 Oct 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Stability: 0.97 → pass security
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.77 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
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 3 Oct 2026 · Analysed npm/@scytalex-llc/pcrzero-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
get_keyset ~79
Returns the current PCRZERO signing keyset — key ids, public halves, and each key's status. Public and unauthenticated: no API key, no cost, no account. This is the same document an outside party fetches to check a PCRZERO receipt without trusting us, and fetching it is how you stop taking our word for anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
issue_receipt ~223
Adjudicates an attestation document against a policy and returns the verdict together with a signed receipt pair — the durable, independently checkable proof that this decision was made, by these keys, over this document. **Metered: every call bills one `receipt_verifications` unit against the API key configured for this server, and a `fail` verdict bills exactly like a `pass`. You are paying for the adjudication, not for the answer you wanted.** This is the only tool here that spends. If you already hold a receipt and want to know whether it is genuine, that is `verify_receipt`, which is free and needs no key.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | – | Base64 attestation document (single-document form). |
| documents | array | – | Base64 attestation documents (batch form). |
| nonce | string | – | – |
| policy | object | – | Inline policy object (API wire shape). |
| policy_id | string | – | Stored policy id (pol_…). |
| receipt | boolean | – | Request a signed receipt (default true). |
No output schema declared.
No examples provided.
verify_receipt ~189
Checks a PCRZERO receipt pair against the signing keyset: whether the signature holds, and whether the receipt says what it appears to say. **Free, with no API key and no account, and it stays free.** Offline by default — supply `keyset` and this call touches the network not at all; omit it and the server fetches the public keyset from api.pcrzero.com once. The result field `keyset_source` tells you which of the two happened, every time. This tool issues nothing, bills nothing, and cannot spend. It is the half of PCRZERO you never pay for.
| Name | Type | Req | Description |
|---|---|---|---|
| conformance | string | – | – |
| keyset | object | – | Optional keyset in GET /v1/keys shape. When supplied, no network is used. |
| receipt | string | yes | Base64url receipt envelope from issue_receipt / the API. |
No output schema declared.
No examples provided.
What is the com.pcrzero/mcp server?
com.pcrzero/mcp is listed in the public MCP registry as com.pcrzero/mcp. Issue signed receipts for AI agent actions; verify any receipt offline - free, no account. This page covers its npm package (@scytalex-llc/pcrzero-mcp).
Is the com.pcrzero/mcp server safe to use?
com.pcrzero/mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. It declares no install or post-install scripts. 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.pcrzero/mcp server expose?
com.pcrzero/mcp exposes 3 tools: issue_receipt, verify_receipt, get_keyset. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Is the com.pcrzero/mcp server still maintained?
com.pcrzero/mcp is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.