com.pcrzero/mcp
REMOTE · MCP.PCRZERO.COM · 2 COMPONENTS · SCANNED AUG 18
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 against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management17
- Stability observed for 5 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.pcrzero.com
claude mcp add --transport http com-pcrzero-mcp https://mcp.pcrzero.com/mcp
[mcp_servers.com-pcrzero-mcp] url = "https://mcp.pcrzero.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pcrzero-mcp": {
"type": "remote",
"url": "https://mcp.pcrzero.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-pcrzero-mcp --url https://mcp.pcrzero.com/mcp --transport streamable-http
mcp_servers:
com-pcrzero-mcp:
url: "https://mcp.pcrzero.com/mcp" {
"mcpServers": {
"com-pcrzero-mcp": {
"type": "http",
"url": "https://mcp.pcrzero.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Aug 26 64
First indexed and scored.
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 18 Aug 2026 · Probed https://mcp.pcrzero.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.pcrzero.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 13 Aug 2026 | 26 Feb 2027 | RSA 2048 | SHA256-RSA | db584cd97ee6428f05f4ebc40f5b6f9 |
| SANs: mcp.pcrzero.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC insecure
Validation of mcp.pcrzero.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pcrzero.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pcrzero.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pcrzero.com/mcp | HTTPS enforced | 301 | https://mcp.pcrzero.com:443/mcp |
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.
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.