Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.pcrzero/mcp

REMOTE · MCP.PCRZERO.COM · 2 COMPONENTS · SCANNED OCT 3

Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Install

How do I install the com.pcrzero/mcp server?

com.pcrzero/mcp is a hosted endpoint at https://mcp.pcrzero.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.pcrzero.com

# add to Claude Code
claude mcp add --transport http com-pcrzero-mcp 'https://mcp.pcrzero.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-pcrzero-mcp": {
      "url": "https://mcp.pcrzero.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-pcrzero-mcp": {
      "type": "http",
      "url": "https://mcp.pcrzero.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-pcrzero-mcp]
url = "https://mcp.pcrzero.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pcrzero-mcp": {
      "type": "remote",
      "url": "https://mcp.pcrzero.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-pcrzero-mcp --url 'https://mcp.pcrzero.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-pcrzero-mcp:
    url: "https://mcp.pcrzero.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-pcrzero-mcp": {
      "Transport": "http",
      "Url": "https://mcp.pcrzero.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-pcrzero-mcp -t streamable-http -u 'https://mcp.pcrzero.com/mcp'
// mcp.json
{
  "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.

Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Sept 26 0
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

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

  • 8 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.

  • 6 Sept 26 +1

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

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 · 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

Background: What to check on a remote MCP endpoint →

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 3 exposed · ~491 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
documentstring–Base64 attestation document (single-document form).
documentsarray–Base64 attestation documents (batch form).
noncestring––
policyobject–Inline policy object (API wire shape).
policy_idstring–Stored policy id (pol_…).
receiptboolean–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.

NameTypeReqDescription
conformancestring––
keysetobject–Optional keyset in GET /v1/keys shape. When supplied, no network is used.
receiptstringyesBase64url receipt envelope from issue_receipt / the API.

No output schema declared.

No examples provided.

Common questions

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 hosted endpoint (https://mcp.pcrzero.com/mcp).

Is the com.pcrzero/mcp server safe to use?

com.pcrzero/mcp scores 79 out of 100 on VerifyMCP. 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.

Does the com.pcrzero/mcp server require authentication?

No. We connected to com.pcrzero/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.