
Proof CLI (unofficial)
io.github.tsarlewey由 GitHub 帳號 tsarlewey 發布v0.4.0更新於 Oct 25, 2026
Notarize, e-sign, and verify identity with the Proof API. Unofficial; not affiliated with Proof.
發布方自己的服務:Proof Holdings
概覽
非官方的 Proof CLI MCP 伺服器,讓助理透過 stdio 呼叫 Proof 的公證、電子簽章、身分驗證、房地產與 SCIM API。
- 可以做什麼
- 管理商務交易與文件:列出、建立、啟用、局部修改、取消或刪除交易,新增或移除文件,檢視範本與成本中心
- 處理公證人、Webhook、推薦活動與整合,包括建立和刪除公證人、註冊 Webhook 位址
- 操作房地產與房貸交易、文件、範本,並驗證地址
- 管理 SCIM 使用者與結構描述,讀取組織的安全事件記錄
- 簽發、使用與撤銷憑證,並產生可驗證憑證的授權連結
- 適用情境
- 適合需要讓助理從命令列驅動 Proof 的公證、電子簽章或身分流程的情境,例如建立簽署交易、管理公證人或 Webhook、管理 SCIM 使用者。此工具處於 alpha 階段且非官方,建議先在沙箱環境評估再用於正式環境。
- 執行需求
- 以本機程序執行:需要把 proof 執行檔放在 PATH 中,或改用已發布的容器映像。需要開通 API 用量的 Proof 帳號與 API 金鑰,透過 PROOF_API_KEY 或 CLI 設定提供;也支援 OAuth 用戶端憑證。可用 PROOF_API_ENDPOINT 指向沙箱位址。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Proof CLI (unofficial),將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Proof CLI
An unofficial command-line interface for interacting with the Proof API. The Proof CLI provides access to Business, Real Estate, and SCIM APIs through a unified interface.
This is an alpha product and should be treated as such. It is not an official product from Proof.
Installation
Prebuilt binary
Windows zips and checksums are on the Releases page.
Install via Go
From Source
Use with AI agents
Claude Code plugin (bundles a usage skill and the MCP server; needs proof on your PATH):
MCP server for any MCP client. proof mcp exposes every API command as a tool over stdio, annotated read-only or destructive:
For other clients, run the command proof mcp. It reads credentials the same way as the CLI (PROOF_API_KEY or proof config).
Docker, with nothing installed locally. The image runs proof mcp and is listed in the MCP Registry as io.github.tsarlewey/proof-cli:
Arguments after the image name go to proof mcp, e.g. --read-only. PROOF_API_ENDPOINT overrides the configured endpoint in any mode; leave it unset for production.
Agents using the shell can follow skills/proof/SKILL.md. Output is JSON (--pretty=false for compact), and API errors exit 1 with the response body on stderr. Point at the sandbox while testing: proof config set-endpoint https://api.fairfax.proof.com.
Getting Started
1. Configuration
Before using the CLI, you need to configure your API key:
In order to get an API Key, you'll need an account with API Usage. You can get that here - https://www.proof.com/pricing#business
After your account is created and upgrade use https://dev.proof.com/docs/api-keys to setup your key.
OAuth 2.0 Authentication
The CLI supports OAuth 2.0 client credentials flow for secure API authentication:
OAuth tokens are automatically refreshed before expiration (5-minute buffer).
2. Basic Usage
The CLI is organized into three main API groups:
business- Business API operations (transactions, documents, webhooks, notaries, etc.)real-estate- Real Estate/Mortgage API operationsscim- SCIM API operations for user management
API Reference
Business API
The Business API provides comprehensive transaction and document management capabilities.
Transactions
Documents
Webhooks
Notaries
Templates
Cost Centers
Referrals
Integrations
Real Estate API
The Real Estate API specializes in mortgage and real estate transaction management.
Transactions
Templates
Cost Centers
Documents
Webhooks
Address Verification
SCIM API
The SCIM API provides standardized user management capabilities.
Users
Schemas
Security Events API
Read the organization's OCSF-formatted security event log.
Certificates API
Issue, use, and revoke organization certificates.
Verifiable Credentials API
Requests a Verifiable Credential presentation from an End-User. This endpoint is a browser redirect, not a server-to-server call — the CLI prints the URL for you to send the End-User to, and does not follow it.
--redirect-uri is required in fragment mode and rejected in direct_post
mode; --response-uri is the reverse. Both URIs must be registered on your
OAuth Application.
Examples
The CLI includes example commands that demonstrate common workflows:
Configuration
The CLI stores configuration in ~/.proof-cli/:
config.json- Main configuration fileapi_key- API key (permissions 0600)
Configuration options:
endpoint- API endpoint URLtimeout- Request timeout in seconds
Global Flags
All commands support these global flags:
--pretty- Pretty print JSON output (default: true)--verbose- Show additional debug output--help- Show help information
Environment Variables
PROOF_API_KEY- API key for authenticationPROOF_ENDPOINT- Override default API endpointPROOF_TIMEOUT- Request timeout in seconds
Error Handling
The CLI provides detailed error messages and uses standard exit codes:
0- Success1- General error (API error, invalid arguments, etc.)
Development
Building from Source
Makefile Targets
The project provides a Makefile for common development tasks:
SDK Source
The generated Go SDK clients now live in their own repo: github.com/tsarlewey/proof-sdk-go. This CLI imports them as a regular Go module dependency. If you need to regenerate the clients after an upstream OpenAPI spec change, work inside the SDK repo — the generation toolchain (OpenAPI specs, oapi-codegen configs, preprocessing scripts, make regenerate) moved there.
To pick up a new SDK release in this CLI:
Adding or Updating Commands
CLI commands live in cmd/ (one file per API surface) and are built with Cobra. Each command's Run closure calls a method on the generated SDK client via the factory helpers in cmd/root.go (getBusinessClient, getRealEstateClient, getSCIMClient). The factories wrap the SDK client with common.AuthenticatedDoer (from the SDK repo), which injects OAuth bearer tokens or the API key on every request.
Shared helpers in cmd/root.go:
initializeForAPICall— lazy client setup, used asPreRunon every API-calling command.PrintResponse/PrintVerbose— response output with optional pretty-printing and colorization.parseDateFlag— parses optional date-flag values, exits with a clear message on parse failure.isSuccess— 2xx status-code check.checkAPIStatus— after every SDK call, exits 1 with the body on stderr if the API returned a non-2xx response.
Errors from SDK calls are funneled through utils.HandleError(err, "action phrase") for transport errors and checkAPIStatus(resp.StatusCode(), resp.Body, "action phrase") for application-level HTTP errors. Both exit 1.
Support
For issues and feature requests, please visit the GitHub repository.
License
來源:README.md,提交 8b5a939
工具
0版本歷史
2- v0.4.0最新Oct 25, 2026
- v0.3.1Sep 30, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。
其他 Proof 整合
Proof Holdings
holdings.proof官方發布者
Proof Holdings MCP 伺服器讓助理發起並管理身分與控制權驗證(手機、電子郵件、網域、錢包),管理證明權杖與委派,並進行驗證。

Proof of Work
由 GitHub 帳號 kivtxs 發布
讓助理閱讀 Proof of Work 的規則、檢查本機是否已有帳號,並建立代理帳號以發佈、投票與支持附證據的主張。

QuietProof
由 GitHub 帳號 frankjie3-create 發布
QuietProof 提供免費探索工具,用來瀏覽一組確定性、唯讀的稽核服務,這些稽核按次以 Base 上的 USDC 透過 x402 付費。
SCRIPTMASTERLABS — 402Proof
com.scriptmasterlabs
遠端 MCP 端點,用於在 XRPL 上以 RLUSD 建立、驗證與評分發票,並對結算進行自證。

ZKStamp Proof-100
由 GitHub 帳號 ZKStamp 發布
遠端 MCP 伺服器,把 SHA-256 指紋以遮蔽交易寫入 BitcoinZ 區塊鏈,產生附日期的存在性證明時間戳。