
Proof CLI (unofficial)
io.github.tsarlewey由 GitHub 账号 tsarlewey 发布v0.4.1更新于 Nov 8, 2026
Notarize, e-sign, and verify identity with the Proof API. Unofficial; not affiliated with Proof.
发布方自己的服务:Proof Holdings
概览
非官方 MCP 服务器,封装 Proof API,让助手创建和管理公证、电子签名与身份验证交易。
- 可以做什么
- 列出、创建、更新、激活、取消和删除商业交易,并添加、获取或删除其文档
- 管理 webhook、公证员、模板、成本中心、推荐活动和集成
- 处理房地产与抵押贷款交易、文档、webhook 及地址验证
- 按组织管理 SCIM 用户与架构
- 读取 OCSF 安全事件日志,并签发、使用或吊销证书
- 生成可验证凭证授权链接,供终端用户在浏览器中跳转
- 适用场景
- 当你希望助手在对话中驱动 Proof 的公证或电子签名流程时使用,例如起草并激活签署交易、附加文档、查询状态,或管理公证员与 webhook。也适合读取 Proof 的安全日志和证书。
- 运行要求
- 以 stdio 本地进程运行,通常使用已发布的容器镜像或 PATH 中的 proof 可执行文件。需要一个开通 API 用量的 Proof 账户和 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版本历史
3- v0.4.1最新Nov 8, 2026
- v0.4.0Oct 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 服务器,让 AI 助手创建身份验证、校验证明令牌并检查域名委托。

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 区块链,生成带日期的存在性证明时间戳。