Proof CLI MCP server
2026년 11월 7일 커밋Proof API를 통해 AI 클라이언트가 공증, 전자 서명, 신원 확인, 비즈니스 트랜잭션, 부동산 문서 및 SCIM 사용자 관리를 수행할 수 있도록 지원합니다.
다른 이름 tsarlewey/proof-cli, proof-cli
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.4.1
- 마지막 커밋
- 2026년 11월 7일
- 라이선스
- —
Proof CLI MCP란?
Proof API를 통해 AI 클라이언트가 공증, 전자 서명, 신원 확인, 비즈니스 트랜잭션, 부동산 문서 및 SCIM 사용자 관리를 수행할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Proof CLI MCP server 정보
Proof CLI는 AI 에이전트와 개발자를 Proof API에 연결하기 위해 설계된 비공식 command-line interface입니다. 비즈니스 트랜잭션, 부동산 문서 및 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를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
OAuth 2.0을 지원하나요?
네, CLI는 자동 토큰 갱신을 포함하여 보안 API 인증을 위한 OAuth 2.0 client credentials flow를 지원합니다.
MCP server에 읽기 전용 모드가 있나요?
네, 데이터를 변경하지 않는 도구만 사용하도록 서버를 읽기 전용 모드로 실행할 수 있습니다.