Proof CLI MCPサーバー
コミット 2026年11月7日Proof APIを介して、AIクライアントによる公証、電子署名、本人確認、ビジネス取引、不動産書類、およびSCIMユーザー管理を可能にします。
別名 tsarlewey/proof-cli, proof-cli
- スター
- 0
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 0.4.1
- 最終コミット
- 2026年11月7日
- ライセンス
- —
Proof CLI MCPとは
Proof APIを介して、AIクライアントによる公証、電子署名、本人確認、ビジネス取引、不動産書類、およびSCIMユーザー管理を可能にします。
プロジェクトのREADMEから生成された概要
Proof CLI MCP server について
Proof CLIは、AIエージェントと開発者をProof APIに接続するために設計された非公式のコマンドラインインターフェースです。ビジネス取引、不動産書類、およびSCIMユーザー管理を統合的に管理する方法を提供します。ユーザーは、Goによるローカルインストールやビルド済みのバイナリ、またはDockerコンテナを実行することでサービスを利用できます。このサーバーは、APIコマンドをstdio経由のツールとして公開するため、AIクライアントは読み取り専用のクエリから破壊的な操作まで、さまざまなアクションを実行できます。
このサーバーを使用するには、PROOF_API_KEYを提供するか、OAuth 2.0の認証情報を設定する必要があります。インターフェースは特定の機能グループに整理されています。ドキュメントと公証管理用のbusiness、住宅ローンに特化したワークフロー用のreal-estate、および標準化されたユーザー管理用のscimです。また、セキュリティイベントログや証明書管理へのアクセスも含まれます。開発者は、AIクライアントがデータを変更しないツールのみにアクセスできるように、サーバーを読み取り専用モードで実行できます。
できること
- 1ビジネス取引の管理AIエージェントは、ビジネス取引の作成、更新、キャンセル、および関連ドキュメントの管理を行うことができます。
- 2不動産ワークフローの処理開発者はこのクライアントを使用して、住宅ローン取引の管理や物件住所の確認を行うことができます。
- 3ユーザープロビジョニングの自動化SCIM標準を使用して、組織内のユーザーの作成、更新、削除をAIに指示できます。
- 4セキュリティログの監視エージェントは、組織のOCSF形式のセキュリティイベントログを取得し、フィルタリングできます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
Proof CLI MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにProof CLI MCPをインストール
$ claude mcp add --env 'PROOF_API_KEY=<YOUR_PROOF_API_KEY>' proof-cli -- docker run -i --rm ghcr.io/tsarlewey/proof-cli:0.4.1CursorにProof CLI MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"proof-cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tsarlewey/proof-cli:0.4.1"
],
"env": {
"PROOF_API_KEY": "<YOUR_PROOF_API_KEY>"
}
}
}
}VS CodeにProof CLI MCPをインストール
.vscode/mcp.json
{
"servers": {
"proof-cli": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tsarlewey/proof-cli:0.4.1"
],
"env": {
"PROOF_API_KEY": "<YOUR_PROOF_API_KEY>"
}
}
}
}VS Code CLIにProof CLI MCPをインストール
$ code --add-mcp '{"name":"proof-cli","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/tsarlewey/proof-cli:0.4.1"],"env":{"PROOF_API_KEY":"<YOUR_PROOF_API_KEY>"}}'Claude DesktopにProof CLI MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"proof-cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tsarlewey/proof-cli:0.4.1"
],
"env": {
"PROOF_API_KEY": "<YOUR_PROOF_API_KEY>"
}
}
}
}CodexにProof CLI MCPをインストール
$ codex mcp add proof-cli --env 'PROOF_API_KEY=<YOUR_PROOF_API_KEY>' -- docker run -i --rm ghcr.io/tsarlewey/proof-cli:0.4.1Codex config.tomlにProof CLI MCPをインストール
~/.codex/config.toml
[mcp_servers.proof-cli] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/tsarlewey/proof-cli:0.4.1"] [mcp_servers.proof-cli.env] PROOF_API_KEY = "<YOUR_PROOF_API_KEY>"
Gemini CLIにProof CLI MCPをインストール
$ gemini mcp add -s user -e 'PROOF_API_KEY=<YOUR_PROOF_API_KEY>' proof-cli docker -- run -i --rm ghcr.io/tsarlewey/proof-cli:0.4.1Gemini settings.jsonにProof CLI MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"proof-cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/tsarlewey/proof-cli:0.4.1"
],
"env": {
"PROOF_API_KEY": "<YOUR_PROOF_API_KEY>"
}
}
}
}設定
PROOF_API_KEY必須シークレットProof API key (https://dev.proof.com/docs/api-keys)
PROOF_API_ENDPOINTAPI base URL. Defaults to production; use https://api.fairfax.proof.com for the sandbox.
| 名前 | 説明 | 種類 |
|---|---|---|
| PROOF_API_KEY | Proof API key (https://dev.proof.com/docs/api-keys) | 必須シークレット |
| PROOF_API_ENDPOINT | API base URL. Defaults to production; use https://api.fairfax.proof.com for the sandbox. |
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能tsarlewey/proof-cli is public and reachablegithub.com/tsarlewey/proof-cli ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)No license検出事項
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-07github.com/tsarlewey/proof-cli ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見る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
# macOS / Linux: downloads the latest release for your OS and CPU into the current directory
curl -sL "https://github.com/tsarlewey/proof-cli/releases/latest/download/proof_$(uname -s | tr A-Z a-z)_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz proof
./proof version
Windows zips and checksums are on the Releases page.
Install via Go
go install github.com/tsarlewey/proof-cli@latest
From Source
git clone https://github.com/tsarlewey/proof-cli.git
cd proof-cli
go build -o proof
./proof --help
Use with AI agents
Claude Code plugin (bundles a usage skill and the MCP server; needs proof on your PATH):
/plugin marketplace add tsarlewey/proof-cli
/plugin install proof@proof
MCP server for any MCP client. proof mcp exposes every API command as a tool over stdio, annotated read-only or destructive:
claude mcp add proof -- proof mcp # Claude Code
claude mcp add proof -- proof mcp --read-only # only tools that don't change anything
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:
docker run -i --rm -e PROOF_API_KEY -e PROOF_API_ENDPOINT=https://api.fairfax.proof.com ghcr.io/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:
# Set your API key
proof config set-api-key YOUR_API_KEY
# Or set via environment variable
export PROOF_API_KEY=YOUR_API_KEY
# Verify your configuration
proof config get
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:
# Configure OAuth credentials
proof config set-oauth <client-id> <client-secret> [--scope="read write"]
# Test OAuth authentication
proof config test-oauth
# Disable OAuth (fallback to API key)
proof config disable-oauth
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
# Get help for any command
proof --help
proof business --help
proof real-estate --help
proof scim --help
API Reference
Business API
The Business API provides comprehensive transaction and document management capabilities.
Transactions
# List all transactions
proof business transactions list
# List with filtering
proof business transactions list --limit 10 --status completed
# Get a specific transaction
proof business transactions get <transaction-id>
# Create a new transaction
proof business transactions create \
--email "signer@example.com" \
--first-name "John" \
--last-name "Doe" \
--document "/path/to/document.pdf" \
--name "Contract Signing" \
--draft
# Multiple documents, scheduled notary meeting, and a redirect
proof business transactions create \
--email "signer@example.com" \
--document "/path/to/deed.pdf" \
--document "/path/to/rider.pdf" \
--notary-meeting-time "2026-09-02T15:30:00Z" \
--allowed-notary-states "CA,NY" \
--notary-note "Verify the property address" \
--payer sender \
--idv-use-case ACCOUNT_RECOVERY \
--recipient-details-config "name=locked" \
--redirect-url "https://example.com/done"
# Multiple signers, from a JSON file holding an array of signer objects
# (max 10, each needs at least an email). --email stays the primary signer.
proof business transactions create \
--email "primary@example.com" \
--document "/path/to/document.pdf" \
--signers-file ./signers.json
# Replace a draft transaction (PUT) -- anything you omit reverts to default
proof business transactions update <transaction-id> \
--name "Contract Signing (revised)" \
--expiry "2026-09-08T10:00:00Z"
# Change individual fields and leave the rest alone (PATCH)
proof business transactions patch <transaction-id> --expiry "2026-09-15T10:00:00Z"
# Reorder documents already attached to a draft
proof business transactions patch <transaction-id> \
--document-order "doc_abc123=1" \
--document-order "doc_def456=2"
# See the full parameter set
proof business transactions create --help
# Activate a draft transaction
proof business transactions activate <transaction-id>
# Delete a transaction
proof business transactions delete <transaction-id>
# Cancel a transaction
proof business transactions cancel <transaction-id>
Documents
# Add a document to a transaction
proof business documents add <transaction-id> /path/to/document.pdf \
--filename "Contract.pdf" \
--requirement "esign" \
--esign-required
# Apply a specific template instead of automatic matching
proof business documents add <transaction-id> /path/to/document.pdf --template-id <template-id>
# Get a document
proof business documents get <transaction-id> <document-id>
# Get document as hosted URL (after completion)
proof business documents get <transaction-id> <document-id> --encoding uri
# Delete a document
proof business documents delete <document-id>
Webhooks
# List webhooks (v2)
proof business webhooks list
# Get webhook details
proof business webhooks get-v2 <webhook-id>
# Create a webhook
proof business webhooks create \
--url "https://example.com/webhook" \
--name "Transaction Updates" \
--events "transaction.created,transaction.completed"
# Update a webhook
proof business webhooks update <webhook-id> \
--url "https://new-url.com/webhook"
# Delete a webhook
proof business webhooks delete <webhook-id>
# Get webhook events
proof business webhooks events <webhook-id>
# List available event subscriptions
proof business webhooks subscriptions
Notaries
# List notaries
proof business notaries list
# List notaries by state
proof business notaries list --state CA
# Get notary details
proof business notaries get <notary-id>
# Create a notary
proof business notaries create \
--email "notary@example.com" \
--first-name "Jane" \
--last-name "Smith" \
--state "CA"
# Delete a notary
proof business notaries delete <notary-id>
Templates
# List document templates
proof business templates list
# List with pagination
proof business templates list --limit 50 --offset 100
Cost Centers
# List cost centers, then attribute a transaction with --cost-center-id
proof business cost-centers list
proof business transactions create --email a@b.com --cost-center-id <id>
Referrals
# Create a referral campaign
proof business referrals create \
--name "Partner Referrals" \
--cover-payment \
--redirect-url "https://example.com/signup"
# Generate a referral code
proof business referrals generate-code <campaign-id> \
--expires-at "2024-12-31T23:59:59Z"
Integrations
# Create an Adobe integration
proof business integrations create \
--name "ADOBE" \
--org-id "your-org-id" \
--account-id "adobe-account-id" \
--environment "production"
# Create a DocuTech integration
proof business integrations create \
--name "DOCUTECH" \
--org-id "your-org-id"
Real Estate API
The Real Estate API specializes in mortgage and real estate transaction management.
Transactions
# List real estate transactions
proof real-estate transactions list
# List with filtering
proof real-estate transactions list --status "in_progress" --limit 20
# Get transaction details
proof real-estate transactions get <transaction-id>
# Create a transaction
proof real-estate transactions create \
--type "purchase" \
--file-number "RE-2024-001" \
--loan-number "LN-2024-001"
# Place an order for a transaction
proof real-estate transactions place-order <transaction-id>
# Cancel a transaction
proof real-estate transactions cancel <transaction-id>
Templates
# List templates
proof real-estate templates list
Cost Centers
proof real-estate cost-centers list
proof real-estate transactions create --cost-center-id <id>
Documents
# List documents
proof real-estate documents list <transaction-id>
# Get document details
proof real-estate documents get <document-id>
# Upload a document
proof real-estate documents upload <transaction-id> /path/to/document.pdf \
--type "purchase_agreement" \
--external-id "PA-001"
Webhooks
# List real estate webhooks
proof real-estate webhooks list
# Create a webhook
proof real-estate webhooks create "https://example.com/re-webhook" \
--subscriptions "transaction.created,document.uploaded"
Address Verification
# Verify an address
proof real-estate verify-address \
--line1 "123 Main St" \
--city "San Francisco" \
--state "CA" \
--postal-code "94102"
SCIM API
The SCIM API provides standardized user management capabilities.
Users
# List users in an organization
proof scim users list <organization-id>
# List with pagination
proof scim users list <organization-id> --start-index 1 --count 25
# Get user details
proof scim users get <organization-id> <user-id>
# Create a user
proof scim users create <organization-id> \
--username "user@example.com" \
--given-name "John" \
--family-name "Doe" \
--email "user@example.com" \
--active
# Update a user (full replacement)
proof scim users update <organization-id> <user-id> \
--username "updated@example.com" \
--given-name "Jane"
# Patch a user (partial update); --operation is repeatable, format op:path[:value]
proof scim users patch <organization-id> <user-id> \
--operation 'replace:active:false'
# Delete a user
proof scim users delete <organization-id> <user-id>
Schemas
# Get user schema
proof scim schemas user <organization-id>
# Get service provider configuration
proof scim schemas service-provider-config <organization-id>
# Get resource types
proof scim schemas resource-types <organization-id>
Security Events API
Read the organization's OCSF-formatted security event log.
# List recent security events
proof logs list
# Page through results
proof logs list --limit 100
proof logs list --cursor <next_cursor-from-previous-response>
# Filter
proof logs list --since 2026-01-01T00:00:00Z
proof logs list --class-uid 1001 --severity-id 3
Certificates API
Issue, use, and revoke organization certificates.
# List certificates
proof certificates list --limit 25 --offset 0
# Get one certificate
proof certificates get <certificate-id>
# Issue a certificate with a Proof-generated key
proof certificates create \
--common-name "Acme Signing Authority" \
--profile organization_authenticity_al2
# Issue a certificate from your own CSR
proof certificates create-from-csr --csr "$(cat request.pem)"
# Sign base64-encoded SHA256 digests (--digest is repeatable, max 25)
proof certificates sign <certificate-id> --digest "BOGQnhPlcpXqM7fAH6tvFPI4QOXsIyXMiBKtFpblmjU="
# Revoke
proof certificates revoke <certificate-id> --reason "key compromise"
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.
# Fragment mode: the vp_token comes back on your redirect URI
proof credentials authorize-url \
--client-id <oauth-client-id> \
--response-mode fragment \
--redirect-uri https://app.example.com/callback \
--scope "openid" \
--login-hint user@example.com \
--nonce "$(openssl rand -hex 16)" \
--state "$(openssl rand -hex 8)"
# direct_post mode: Proof POSTs the vp_token to your response URI
proof credentials authorize-url \
--client-id <oauth-client-id> \
--response-mode direct_post \
--response-uri https://app.example.com/vp \
--scope "openid" \
--login-hint user@example.com \
--nonce "$(openssl rand -hex 16)"
--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:
# List all available examples
proof example --help
# Business API examples
proof example business-transactions # List business transactions
proof example business-notary # Create a notary
# Real Estate API examples
proof example real-estate-transactions # List real estate transactions
proof example verify-address # Verify an address
# SCIM API examples
proof example scim-users <org-id> # List SCIM users
proof example scim-schema <org-id> # Get SCIM user schema
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
# View current configuration
proof config get
# Set API endpoint
proof config set-endpoint "https://api.proof.com"
# Set request timeout
proof config set-timeout 30
# Set API key
proof config set-api-key "your-api-key"
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
git clone https://github.com/tsarlewey/proof-cli.git
cd proof-cli
go mod download
go build -o proof
Makefile Targets
The project provides a Makefile for common development tasks:
make build # Build the ./proof binary
make install # Install the CLI via go install
make fmt # Run go fmt
make vet # Run go vet
make test # Run all tests
make test-race # Run all tests with -race
make coverage # Run tests with coverage profile
make check # fmt + vet + build + test-race
make clean # Remove the built binary
make smoke # Run shell smoke tests against live API
make smoke-go # Run Go smoke tests (build-tag smoke)
make smoke-write # Run shell write smoke tests (PROOF_SMOKE_WRITE=1)
make smoke-write-go # Run Go write smoke tests (build-tag smoke_write)
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:
go get github.com/tsarlewey/proof-sdk-go@<new-version>
go mod tidy
make check
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
Proof CLI MCPのよくある質問
Proof CLI MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --env 'PROOF_API_KEY=<YOUR_PROOF_API_KEY>' proof-cli -- docker run -i --rm ghcr.io/tsarlewey/proof-cli:0.4.1を実行します。すべてのプロジェクトで利用するには--scope userを追加します。
Proof CLI MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
このMCP serverはOAuth 2.0をサポートしていますか?
はい、CLIはOAuth 2.0のクライアント資格情報フローをサポートしており、自動トークンリフレッシュを含む安全なAPI認証が可能です。
MCP serverに読み取り専用モードはありますか?
はい、データの変更を伴わないツールのみを使用するように、サーバーを読み取り専用モードで実行できます。