POPCORN Witness Verifier

io.github.violetclaire由 GitHub 账号 violetclaire 发布v2.0.1更新于 Oct 27, 2026

MCP server for verifying receipts: POPCORN-WITNESS/2.0 signature, digest, and time. Free, read only.

已验证Streamable HTTP可网页运行金融安全与监控

概览

AI 生成的概览

用于校验 POPCORN-WITNESS/2.0 签名时间与摘要凭证的服务器,让助手用调用方自备的密钥核对某项操作确实在所述时间发生。

可以做什么
  • 用期望的 SHA-256 摘要、nonce 和独立获取的签发方密钥校验 POPCORN-WITNESS/2.0 凭证,并支持链式前序凭证
  • 在本地对精确字节计算 SHA-256 摘要与字节长度
  • 离线校验较早的时间凭证或见证凭证,对照调用方提供的密钥与期望值
  • 运行内置示例凭证与篡改对照,作为可复现的评估
  • 获取线上服务目录、公开 JWKS 与公开 schema
  • 申请新的签名时间参考或新的见证凭证(默认试运行,明确批准后才付费)
适用场景
当助手或代理需要核对他方转来的签名凭证、确认某份载荷在所述时间已存在,或为截止时间、授权到期获取新的签名时间参考时使用。校验为只读,任何接收方都可重复执行,无需在原始服务方开户。
运行要求
可通过 streamable HTTP 连接远程端点,或用 Node.js 20 及以上运行 npm 包。免费工具、试运行和离线校验无需账户或钱包。付费的时间与见证调用需要在服务器进程环境中以 EVM_PRIVATE_KEY 提供专用的 Base 付款私钥,并需要网络访问。
安装前请注意
付费调用会在 Base 上花费 0.001 USDC,且只有该次调用显式设置 approve_payment 为 true 才会执行;EVM_PRIVATE_KEY 应专用、余额少,且不要粘贴到工具调用或聊天中。调用方自备的密钥不能确立签发方身份,校验通过也不证明链上结算或授予权限。远程 HTTP 端点只接受摘要,不接受载荷字节。内置示例密钥与凭证仅用于复现,并不测试当前部署的服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 POPCORN Witness Verifier,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.violetclaire%2Fpopcorn-tain-verifier/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "popcorn-witness-verifier": {
      "type": "http",
      "url": "https://popcorn-tain-verify-mcp-v2.violetherod.workers.dev/mcp"
    }
  }
}

README

Briarwood AI / POPCORN MCP server

For RFC 3161, FreeTSA, OpenTimestamps, a trusted timestamp, proof of existence, authorization expiry, a signed execution receipt, or independent verification, start with Proving an action happened before an authorization expired.

Read-only time and task evidence from Briarwood AI, usable across independent agents. POPCORN supplies signed time and digest checkpoints at https://767-2676.com.

Try it first, without a wallet

Save sample.mjs, read it, then run node sample.mjs with Node.js 20 or newer. This standalone sample includes an exact eight-line schedule with who, its SHA-256 digest, and a real signed receipt. It runs offline and rejects a one-byte change to who.

The plain-text contract and full packet can be retained locally. The receipt is historical evidence. Fetch new time for a new decision.

Run the current source from this public repository:

bash
git clone https://github.com/violetclaire/popcorn-temporal-anchor.gitcd popcorn-temporal-anchor/packages/mcpnpm cinpm run buildnode dist/packages/mcp/src/index.js --sample

After version 0.1.4 is published to npm, run:

bash
npx -y @violetclaire/[email protected] --sample

The evaluation checks the eight-line task schedule and two legacy, historically settled receipts with the maintained verifier. It returns valid signatures, STOP for a checkpoint after its task window, TIME_CHECK_PASSED for one inside its window, and a rejected one-byte change for each. Every result retains authorization_granted: false. The sample needs no account, wallet, or original task data. npm may download the package; the verification itself runs entirely offline.

Inside a connected MCP client, call popcorn_sample with {} for the same result. Its public source links let another developer repeat the check. The bundled historical keys are for sample reproduction. A real task requires independently trusted issuer keys; an old receipt is not a fresh clock reading. This offline sample tests historical pre-TAIN receipts only. Passing it does not test the currently deployed TAIN 2.0 service or establish integration readiness.

Use it for a real task

NeedToolWhat stays local
A fresh, signed time reference for a deadline or expirypopcorn_timeThe task and decision
Evidence of one exact task version at a stated timepopcorn_hash, then popcorn_witnessRaw task bytes; only the digest, nonce, and optional predecessor digest go to the witness
Check evidence received from another agentpopcorn_verifyThe receipt, trusted keys, payload, and verification
Check a TAIN 2.0 witness receiptpopcorn_verify_v2 or local CLI verify-v2Exact expected bytes and independently trusted keys

These uses apply across agent providers and industries. Share a receipt and the relevant exact bytes through your existing authorized handoff, then let the receiving system verify them. No account at the originating agent provider is required for offline verification. Each participant decides what to do.

This source checkout exposes five free tools and two x402 tools. The x402 tools are dry run by default. They cannot spend unless the individual tool call contains approve_payment: true. A wallet key is read only from EVM_PRIVATE_KEY in the server process environment. It is never accepted as a tool parameter.

This is a clock and a seal. It does not refund, authorize, or hold funds.

Run with npx

Install and run the published package with:

bash
npx -y @violetclaire/popcorn-mcp

Node.js 20 or newer is required.

Programmatic core

The supported @violetclaire/popcorn-mcp/core export exposes the same local hashing, offline verification, and paid client functions used by the stdio server:

ts
import {  popcornHash,  popcornVerifyWitnessChain,  popcornWitness,} from "@violetclaire/popcorn-mcp/core";

popcornVerifyWitnessChain accepts receipts in chronological order, starting with a receipt whose previous_attestation_digest is null. It verifies each receipt and signature once, checks each link against the prior receipt's exact signed-payload bytes, and returns the verified entries plus the head digest. It is free, local, and sends no network request.

Tools

popcorn_sample

Runs the two public receipt examples and their tamper controls locally. This is a reproducible evaluation of historical evidence and makes no network request or payment. Input: {}. Its historical receipts are not a TAIN 2.0 conformance test.

popcorn_verify_v2

Verifies a POPCORN-WITNESS/2.0 signed envelope, required TAIN fields, exact expected payload digest and nonce, and the signed time interval. Both this local MCP tool and popcorn-mcp verify-v2 <vector.json> call the same verifier. The fixed positive and negative vectors under verify/test-vectors/interface-parity-v2/ run through both interfaces in npm run check and fail the check on any result or reason mismatch.

Provide the full response, expected SHA-256 payload digest as canonical unpadded base64url, the expected nonce, and issuer keys obtained independently of the receipt. The local CLI and stdio MCP also accept exact payload bytes as expected_payload_base64url instead of a digest; the remote HTTP MCP accepts only a digest, including for predecessor receipts, so private payload bytes need not leave the caller. Supply previous_receipt with its own response, JWKS, and verification inputs for a chained receipt, up to eight links. Caller-supplied keys alone do not establish issuer identity; this verifier does not prove on-chain settlement or grant authority.

popcorn_catalog

Fetches the live service catalog, published JWKS, and public schemas. It is free and sends no payment.

Input:

json
{}

popcorn_hash

Hashes exact bytes locally and returns the SHA-256 digest plus byte length. It is free, local, and sends no network request.

Provide exactly one input form:

json
{ "payload_text": "exact UTF-8 text" }
json
{ "payload_base64url": "ZXhhY3QgYnl0ZXM" }

popcorn_verify

Verifies a POPCORN temporal or witness receipt locally against caller-supplied keys and expected values. It is free, local, and sends no payment.

For a witness receipt:

json
{  "receipt_type": "witness",  "response": { "witness_receipt": {}, "witness_attestation": {}, "payment_status": "settled" },  "jwks": { "keys": [] },  "verification": {    "expected_nonce": "<43-character-base64url>",    "expected_payload_base64url": "<exact-payload-bytes>",    "expected_node_id": "767-2676.com",    "max_clock_accuracy_radius_ms": 10000  }}

Provide exactly one of expected_payload_text, expected_payload_base64url, or expected_payload_digest.

When previous_attestation_digest is non-null, add this recursively under verification:

json
{  "previous_receipt": {    "response": { "witness_receipt": {}, "witness_attestation": {}, "payment_status": "settled" },    "jwks": { "keys": [] },    "verification": {      "expected_nonce": "<predecessor-nonce>",      "expected_payload_digest": "<predecessor-payload-digest>"    }  }}

The verifier first verifies the predecessor. It then hashes the exact bytes obtained by base64url-decoding the predecessor compact JWS payload segment and compares that digest with previous_attestation_digest.

For a temporal receipt, verification.observation carries the monotonic timer values required by the existing offline verifier. An optional verification.policy can carry execution_window_utc.

popcorn_time

Requests GET /v1/time. The default call is a free dry run:

json
{  "freshness_ms": 30000,  "approve_payment": false}

It returns the HTTP 402 terms and the exact request that would be paid. To authorize one payment, the caller must set approve_payment to true in that specific call.

popcorn_witness

Requests POST /v2/receipt. POST /v1/receipt remains available to existing integrations. The default call is a free dry run:

json
{  "digest": "<43-character-sha256-base64url>",  "nonce": "<43-character-random-base64url>",  "previous_attestation_digest": null,  "approve_payment": false}

The optional predecessor digest is SHA-256 over the exact decoded signed payload bytes of the predecessor compact JWS. It is not a digest of the full compact JWS string.

Both paid tools lock payment to exactly $0.001 USDC on Base, the published USDC contract, and POPCORN's published payTo. A changed challenge fails closed. A successful paid result includes the settlement transaction hash and server_processing_duration_ms.

Wallet environment

Paid calls require:

text
EVM_PRIVATE_KEY=0x<dedicated-32-byte-Base-payer-key>

Use a dedicated payer with a small balance. Do not commit this value. The free tools and all dry runs work without it.

Claude Desktop

Add this server to the mcpServers object in Claude Desktop's configuration:

json
{  "mcpServers": {    "popcorn": {      "command": "npx",      "args": ["-y", "@violetclaire/popcorn-mcp"]    }  }}

That configuration supports all free tools and dry runs. For paid calls, launch Claude Desktop from an environment containing EVM_PRIVATE_KEY, or add an env object to its private local configuration. Never paste the key into a tool call or chat.

Claude Code

bash
claude mcp add --transport stdio popcorn -- npx -y @violetclaire/popcorn-mcp

Set EVM_PRIVATE_KEY in the environment that launches Claude Code only when paid calls are needed. Every paid call still requires approve_payment: true.

Local development

From packages/mcp:

bash
npm installnpm run checknpm start

The package build includes the repository's existing TypeScript verifier in the published files. Runtime dependencies remain normal npm dependencies.

来源:packages/mcp/README.md,提交 432c016

工具

1

popcorn_verify_v2

Verify a TAIN 2.0 witness receipt

Verify a POPCORN-WITNESS/2.0 receipt against a caller-computed SHA-256 payload digest, nonce, and independently trusted issuer keys. Send only the digest, never private payload bytes. Caller-supplied keys do not establish issuer identity. This does not prove on-chain settlement, establish current time, or grant authority. Free and read-only.

输入参数jwks必填response必填expected_nonce必填expected_node_idprevious_receiptexpected_payload_digest必填max_clock_accuracy_radius_ms

版本历史

2
  1. v2.0.1最新Oct 18, 2026
  2. v2.0.0Oct 18, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。