Proof CLI (unofficial)
OCI · GHCR.IO/TSARLEWEY/PROOF-CLI
Notarize, e-sign, and verify identity with the Proof API. Unofficial; not affiliated with Proof.
Available components
Last scanned (11 hours ago)
Scores higher than 84% of OCI servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6362 tokens (~106/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed oci/ghcr.io/tsarlewey/proof-cli@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
business_documents_add ~303
Add a document to a transaction Add a document to an existing transaction CLI equivalent: proof business documents add
| Name | Type | Req | Description |
|---|---|---|---|
| authorization-header | string | – | Header for fetching doc URLs (format: header_name:header_value) |
| bundle-position | integer | – | Position in document bundle |
| customer-can-annotate | boolean | – | Whether signer can add annotations |
| esign-required | boolean | – | Whether e-signature is required |
| file-path | string | yes | Positional argument file-path |
| filename | string | – | Plain language name for the document |
| identity-confirmation-required | boolean | – | Whether identity confirmation is required |
| notarization-required | boolean | – | Whether notarization is required |
| pdf-bookmarked | boolean | – | Whether document is bookmarked PDF (splits by bookmarks) |
| requirement | string | – | Completion requirement (notarization, esign, identity_confirmation, readonly, non_essential) |
| signing-requires-meeting | boolean | – | Whether signing requires a meeting |
| template-id | string | – | Apply this template's designations instead of automatic matching (see: business templates list) |
| text-tag-syntax | string | – | Syntax used by text tags |
| tracking-id | string | – | External tracking identifier |
| transaction-id | string | yes | Positional argument transaction-id |
| vaulted | boolean | – | Whether to store authoritative copy in eVault |
| witness-required | boolean | – | Whether additional witness must be present |
No output schema declared.
No examples provided.
business_documents_delete ~41
Delete a document Delete a document from a transaction CLI equivalent: proof business documents delete
| Name | Type | Req | Description |
|---|---|---|---|
| document-id | string | yes | Positional argument document-id |
No output schema declared.
No examples provided.
business_documents_get ~82
Get a document Get a document from a transaction CLI equivalent: proof business documents get
| Name | Type | Req | Description |
|---|---|---|---|
| document-id | string | yes | Positional argument document-id |
| encoding | string | – | Can be 'base64' or 'uri'. 'uri' returns hosted URL (only after transaction completion) |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_integrations_create ~77
Create an integration Create a new integration for your organization CLI equivalent: proof business integrations create
| Name | Type | Req | Description |
|---|---|---|---|
| account-id | string | – | Integration account ID |
| environment | string | – | Integration environment |
| name | string | – | Integration name (ADOBE or DOCUTECH) |
| org-id | string | – | Organization ID |
No output schema declared.
No examples provided.
business_notaries_create ~95
Create a notary Create a new notary for your organization CLI equivalent: proof business notaries create
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Notary's email address | |
| first-name | string | – | Notary's first name |
| last-name | string | – | Notary's last name |
| middle-name | string | – | Notary's middle name |
| state | string | – | Two-letter state abbreviation |
No output schema declared.
No examples provided.
business_notaries_delete ~48
Delete a notary Delete a specific notary from your organization CLI equivalent: proof business notaries delete
| Name | Type | Req | Description |
|---|---|---|---|
| notary-id | string | yes | Positional argument notary-id |
No output schema declared.
No examples provided.
business_notaries_get ~47
Get a notary Get details of a specific notary CLI equivalent: proof business notaries get
| Name | Type | Req | Description |
|---|---|---|---|
| notary-id | string | yes | Positional argument notary-id |
No output schema declared.
No examples provided.
business_notaries_list ~52
List notaries List all notaries for your organization CLI equivalent: proof business notaries list
| Name | Type | Req | Description |
|---|---|---|---|
| org-id | string | – | Organization ID |
| state | string | – | Two-letter state abbreviation |
No output schema declared.
No examples provided.
business_referrals_create ~119
Create a referral campaign Create a new referral campaign for your organization CLI equivalent: proof business referrals create
| Name | Type | Req | Description |
|---|---|---|---|
| cover-payment | boolean | – | Will the organization pay for these referred transactions? |
| name | string | – | Name of the new campaign (required) |
| organization-id | string | – | ID of organization to create the campaign for (child orgs only) |
| redirect-url | string | – | URL that customers will be sent to from the referral |
| use-branding | boolean | – | Will the referred transactions display the orgs branding? |
No output schema declared.
No examples provided.
business_referrals_generate_code ~79
Generate a referral code Generate a single use referral link for a campaign CLI equivalent: proof business referrals generate-code
| Name | Type | Req | Description |
|---|---|---|---|
| expires-at | string | – | ISO 8601 timestamp for when the code should expire (default: 3 months from creation) |
| referral-campaign-id | string | yes | Positional argument referral-campaign-id |
No output schema declared.
No examples provided.
business_templates_list ~65
List templates List all document templates for your organization CLI equivalent: proof business templates list
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return (default: 100, max: 1000) |
| offset | integer | – | Number of results to skip for pagination |
No output schema declared.
No examples provided.
business_transactions_activate ~87
Activate a draft transaction Activate a draft transaction to send it to the signer CLI equivalent: proof business transactions activate
| Name | Type | Req | Description |
|---|---|---|---|
| require-new-signer-verification | boolean | – | Require the signer to verify email ownership |
| suppress-email | boolean | – | Don't email the signer on activation (you must supply transaction_access_link yourself) |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_cancel ~34
Cancel a transaction CLI equivalent: proof business transactions cancel
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_create ~613
Create a business transaction Create a new transaction with signers and documents CLI equivalent: proof business transactions create
| Name | Type | Req | Description |
|---|---|---|---|
| activation-time | string | – | ISO-8601 datetime when signer can connect with notary |
| allowed-notary-states | array | – | Two-letter state codes the notary may be commissioned in |
| auth-requirement | string | – | Authentication requirement (sms or none) |
| cc-recipient-emails | array | – | Email addresses to CC on transaction notifications |
| config-id | string | – | Transaction configuration ID |
| cosigner-first-name | string | – | Cosigner's first name |
| cosigner-last-name | string | – | Cosigner's last name |
| cosigner-signing-requirement | string | – | Cosigner signing requirement (esign, identify, or verify) |
| document | array | – | Path to a document file; repeat for multiple (required) |
| draft | boolean | – | Create transaction as draft |
| string | – | Primary signer's email address (required on create) | |
| expiry | string | – | ISO-8601 datetime after which transaction expires |
| external-id | string | – | External system ID |
| first-name | string | – | Signer's first name |
| idv-use-case | string | – | Identity verification use case (STANDARD or ACCOUNT_RECOVERY) |
| last-name | string | – | Signer's last name |
| message-signature | string | – | Signature block appended to notification emails |
| message-subject | string | – | Email subject line |
| message-to-signer | string | – | Message to signer (GitHub Flavored Markdown) |
| middle-name | string | – | Signer's middle name |
| name | string | – | Transaction name |
| notary-id | string | – | Assign a specific notary by ID |
| notary-meeting-time | string | – | Scheduled notary meeting time (RFC 3339) |
| notary-note | array | – | Instruction note for the notary; repeat for multiple |
| organization-id | string | – | Act on behalf of a child organization |
| payer | string | – | Who pays for the transaction (signer or sender) |
| pdf-bookmarked | boolean | – | Split the uploaded PDF into documents by its bookmarks |
| phone-number | string | – | Signer's phone number |
| recipient-details-config | array | – | Recipient field display rule as field=display (e.g. name=locked) |
| redirect-message | string | – | Message shown to the signer before redirecting |
| redirect-url | string | – | URL to send the signer to after completion |
| require-new-signer-verification | boolean | – | Require the signer to verify email ownership |
| require-secondary-photo-id | boolean | – | Require two forms of photo ID |
| signers-file | string | – | Path to a JSON file holding an array of additional signer objects (max 10) |
| suppress-email | boolean | – | Don't send notification email on activation |
| type | string | – | Transaction type |
No output schema declared.
No examples provided.
business_transactions_delete ~40
Delete a business transaction Delete a specific transaction CLI equivalent: proof business transactions delete
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_eligible_notaries ~53
Get eligible notaries for a transaction Get all eligible notaries for a specific transaction CLI equivalent: proof business transactions eligible-notaries
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_get ~42
Get a business transaction Get details of a specific transaction CLI equivalent: proof business transactions get
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_list ~135
List business transactions List all transactions for your organization CLI equivalent: proof business transactions list
| Name | Type | Req | Description |
|---|---|---|---|
| created-end | string | – | Filter by created date end (YYYY-MM-DD) |
| created-start | string | – | Filter by created date start (YYYY-MM-DD) |
| last-updated-end | string | – | Filter by last updated date end (YYYY-MM-DD) |
| last-updated-start | string | – | Filter by last updated date start (YYYY-MM-DD) |
| limit | integer | – | Number of transactions to return |
| offset | integer | – | Offset for pagination |
| status | string | – | Filter by transaction status |
No output schema declared.
No examples provided.
business_transactions_patch ~653
Update individual fields on a draft transaction Update a draft transaction in place (HTTP PATCH). Only the parameters you pass are sent; everything else keeps its current value. Use "update" to replace the whole transaction. CLI equivalent: proof business transactions patch
| Name | Type | Req | Description |
|---|---|---|---|
| activation-time | string | – | ISO-8601 datetime when signer can connect with notary |
| allowed-notary-states | array | – | Two-letter state codes the notary may be commissioned in |
| auth-requirement | string | – | Authentication requirement (sms or none) |
| cc-recipient-emails | array | – | Email addresses to CC on transaction notifications |
| config-id | string | – | Transaction configuration ID |
| cosigner-first-name | string | – | Cosigner's first name |
| cosigner-last-name | string | – | Cosigner's last name |
| cosigner-signing-requirement | string | – | Cosigner signing requirement (esign, identify, or verify) |
| document-order | array | – | Reposition an attached document as id=position (e.g. doc_abc123=1) |
| string | – | Primary signer's email address (required on create) | |
| expiry | string | – | ISO-8601 datetime after which transaction expires |
| external-id | string | – | External system ID |
| first-name | string | – | Signer's first name |
| idv-use-case | string | – | Identity verification use case (STANDARD or ACCOUNT_RECOVERY) |
| last-name | string | – | Signer's last name |
| message-signature | string | – | Signature block appended to notification emails |
| message-subject | string | – | Email subject line |
| message-to-signer | string | – | Message to signer (GitHub Flavored Markdown) |
| middle-name | string | – | Signer's middle name |
| name | string | – | Transaction name |
| notary-id | string | – | Assign a specific notary by ID |
| notary-meeting-time | string | – | Scheduled notary meeting time (RFC 3339) |
| notary-note | array | – | Instruction note for the notary; repeat for multiple |
| organization-id | string | – | Act on behalf of a child organization |
| payer | string | – | Who pays for the transaction (signer or sender) |
| pdf-bookmarked | boolean | – | Split the uploaded PDF into documents by its bookmarks |
| phone-number | string | – | Signer's phone number |
| recipient-details-config | array | – | Recipient field display rule as field=display (e.g. name=locked) |
| redirect-message | string | – | Message shown to the signer before redirecting |
| redirect-url | string | – | URL to send the signer to after completion |
| require-new-signer-verification | boolean | – | Require the signer to verify email ownership |
| require-secondary-photo-id | boolean | – | Require two forms of photo ID |
| signers-file | string | – | Path to a JSON file holding an array of additional signer objects (max 10) |
| suppress-email | boolean | – | Don't send notification email on activation |
| transaction-id | string | yes | Positional argument transaction-id |
| type | string | – | Transaction type |
No output schema declared.
No examples provided.
business_transactions_recall ~56
Recall a transaction Recall a transaction with an optional reason CLI equivalent: proof business transactions recall
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Optional reason for recalling the transaction |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_resend_email ~59
Resend transaction email Resend the transaction email with an optional message CLI equivalent: proof business transactions resend-email
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional message to signer |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_resend_sms ~64
Resend transaction SMS Resend the transaction SMS with optional phone parameters CLI equivalent: proof business transactions resend-sms
| Name | Type | Req | Description |
|---|---|---|---|
| phone-number | string | – | Optional phone number to send SMS to |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
business_transactions_update ~655
Replace a draft transaction Replace a draft transaction with the values you supply (HTTP PUT). Any parameter you don't pass is cleared to the API's default. Use "patch" to change individual fields and leave the rest alone. CLI equivalent: proof business transactions update
| Name | Type | Req | Description |
|---|---|---|---|
| activation-time | string | – | ISO-8601 datetime when signer can connect with notary |
| allowed-notary-states | array | – | Two-letter state codes the notary may be commissioned in |
| auth-requirement | string | – | Authentication requirement (sms or none) |
| cc-recipient-emails | array | – | Email addresses to CC on transaction notifications |
| config-id | string | – | Transaction configuration ID |
| cosigner-first-name | string | – | Cosigner's first name |
| cosigner-last-name | string | – | Cosigner's last name |
| cosigner-signing-requirement | string | – | Cosigner signing requirement (esign, identify, or verify) |
| document-order | array | – | Reposition an attached document as id=position (e.g. doc_abc123=1) |
| string | – | Primary signer's email address (required on create) | |
| expiry | string | – | ISO-8601 datetime after which transaction expires |
| external-id | string | – | External system ID |
| first-name | string | – | Signer's first name |
| idv-use-case | string | – | Identity verification use case (STANDARD or ACCOUNT_RECOVERY) |
| last-name | string | – | Signer's last name |
| message-signature | string | – | Signature block appended to notification emails |
| message-subject | string | – | Email subject line |
| message-to-signer | string | – | Message to signer (GitHub Flavored Markdown) |
| middle-name | string | – | Signer's middle name |
| name | string | – | Transaction name |
| notary-id | string | – | Assign a specific notary by ID |
| notary-meeting-time | string | – | Scheduled notary meeting time (RFC 3339) |
| notary-note | array | – | Instruction note for the notary; repeat for multiple |
| organization-id | string | – | Act on behalf of a child organization |
| payer | string | – | Who pays for the transaction (signer or sender) |
| pdf-bookmarked | boolean | – | Split the uploaded PDF into documents by its bookmarks |
| phone-number | string | – | Signer's phone number |
| recipient-details-config | array | – | Recipient field display rule as field=display (e.g. name=locked) |
| redirect-message | string | – | Message shown to the signer before redirecting |
| redirect-url | string | – | URL to send the signer to after completion |
| require-new-signer-verification | boolean | – | Require the signer to verify email ownership |
| require-secondary-photo-id | boolean | – | Require two forms of photo ID |
| signers-file | string | – | Path to a JSON file holding an array of additional signer objects (max 10) |
| suppress-email | boolean | – | Don't send notification email on activation |
| transaction-id | string | yes | Positional argument transaction-id |
| type | string | – | Transaction type |
No output schema declared.
No examples provided.
business_webhooks_create ~95
Create webhook v2 Create a new webhook v2 CLI equivalent: proof business webhooks create
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event subscriptions to subscribe to |
| header | string | – | Header value to pass through every request (e.g. X-Custom-Header:X-Custom-Key) |
| name | string | – | Webhook name (deprecated, use subscriptions) |
| url | string | – | Webhook URL |
No output schema declared.
No examples provided.
business_webhooks_delete ~43
Delete webhook v2 Delete a webhook v2 CLI equivalent: proof business webhooks delete
| Name | Type | Req | Description |
|---|---|---|---|
| webhook-id | string | yes | Positional argument webhook-id |
No output schema declared.
No examples provided.
business_webhooks_events ~47
Get webhook v2 events Get events for a specific webhook v2 CLI equivalent: proof business webhooks events
| Name | Type | Req | Description |
|---|---|---|---|
| webhook-id | string | yes | Positional argument webhook-id |
No output schema declared.
No examples provided.
business_webhooks_get ~31
Get webhook URL Retrieve the webhook URL for your organization CLI equivalent: proof business webhooks get
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
business_webhooks_get_v2 ~51
Get webhook v2 details Get details of a specific webhook v2 CLI equivalent: proof business webhooks get-v2
| Name | Type | Req | Description |
|---|---|---|---|
| webhook-id | string | yes | Positional argument webhook-id |
No output schema declared.
No examples provided.
business_webhooks_list ~35
List webhooks v2 List all webhooks v2 for your organization CLI equivalent: proof business webhooks list
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
business_webhooks_subscriptions ~34
Get webhook v2 subscriptions Get available webhook v2 event subscriptions CLI equivalent: proof business webhooks subscriptions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
business_webhooks_update ~105
Update webhook v2 Update an existing webhook v2 CLI equivalent: proof business webhooks update
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event subscriptions to subscribe to |
| header | string | – | Header value to pass through every request (e.g. X-Custom-Header:X-Custom-Key) |
| name | string | – | Webhook name (deprecated) |
| url | string | – | Webhook URL |
| webhook-id | string | yes | Positional argument webhook-id |
No output schema declared.
No examples provided.
certificates_create ~74
Create a certificate (Proof-generated key) Create a certificate where Proof generates the key pair, identified by a common name CLI equivalent: proof certificates create
| Name | Type | Req | Description |
|---|---|---|---|
| common-name | string | yes | CN field of the subject - required |
| profile | string | – | Certificate profile: organization_authenticity_al1 through _al4 |
No output schema declared.
No examples provided.
certificates_create_from_csr ~83
Create a certificate from a CSR (bring your own key) Create a certificate from a PEM-encoded Certificate Signing Request you generated yourself CLI equivalent: proof certificates create-from-csr
| Name | Type | Req | Description |
|---|---|---|---|
| csr | string | yes | PEM-encoded Certificate Signing Request - required |
| profile | string | – | Certificate profile: organization_authenticity_al1 through _al4 |
No output schema declared.
No examples provided.
certificates_get ~39
Get a certificate Get details of a specific certificate CLI equivalent: proof certificates get
| Name | Type | Req | Description |
|---|---|---|---|
| certificate-id | string | yes | Positional argument certificate-id |
No output schema declared.
No examples provided.
certificates_list ~46
List certificates List the organization's certificates with optional pagination CLI equivalent: proof certificates list
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size |
| offset | integer | – | 0-based offset |
No output schema declared.
No examples provided.
certificates_revoke ~55
Revoke a certificate Revoke a certificate, optionally recording a reason CLI equivalent: proof certificates revoke
| Name | Type | Req | Description |
|---|---|---|---|
| certificate-id | string | yes | Positional argument certificate-id |
| reason | string | – | Reason for revocation |
No output schema declared.
No examples provided.
certificates_sign ~100
Sign digests with a certificate Sign up to 25 base64-encoded SHA256 digests with the given certificate CLI equivalent: proof certificates sign
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm-oid | string | – | Signing algorithm OID (only ECDSA with SHA256 is supported) |
| certificate-id | string | yes | Positional argument certificate-id |
| digest | array | yes | Base64-encoded SHA256 digest (repeatable, max 25) - required |
No output schema declared.
No examples provided.
credentials_authorize_url ~245
Build the Verifiable Credential presentation authorize URL Build the URL that requests a Verifiable Credential presentation from an End-User. This endpoint is a browser redirect, not a server-to-server API call — the CLI prints the URL rather than following it. Send the End-User to the printed URL; Proof returns the vp_token to your redirect_uri or response_uri. CLI equivalent: proof credentials authorize-url
| Name | Type | Req | Description |
|---|---|---|---|
| client-id | string | yes | Your Proof OAuth Application Client ID - required |
| login-hint | string | yes | Email address of the End-User to request a presentation from - required |
| nonce | string | yes | Opaque client-generated value bound to the response to prevent replay - required |
| redirect-uri | string | – | Redirect URI receiving the vp_token fragment (required for fragment mode) |
| response-mode | string | – | How the presentation is returned: fragment or direct_post |
| response-uri | string | – | URI Proof POSTs the vp_token to (required for direct_post mode) |
| scope | string | yes | Space-separated scopes that translate to DCQL queries - required |
| state | string | – | Opaque value echoed back on the callback |
No output schema declared.
No examples provided.
logs_list ~125
List security events List security events with optional filtering and cursor-based pagination CLI equivalent: proof logs list
| Name | Type | Req | Description |
|---|---|---|---|
| class-uid | integer | – | Filter by OCSF event class identifier |
| cursor | string | – | Pagination cursor from a previous response's next_cursor |
| limit | integer | – | Number of events per page (1-1000, default 100) |
| severity-id | integer | – | Filter by OCSF severity identifier |
| since | string | – | ISO 8601 timestamp; only events at or after this time (max 90 days back) |
No output schema declared.
No examples provided.
real_estate_documents_get ~76
Get a real estate document Get details of a specific real estate document CLI equivalent: proof real-estate documents get
| Name | Type | Req | Description |
|---|---|---|---|
| document-id | string | yes | Positional argument document-id |
| encoding | string | – | Encoding format (base64 or uri) |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_documents_list ~51
List real estate documents for a transaction List real estate documents for a specific transaction CLI equivalent: proof real-estate documents list
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_documents_upload ~75
Upload a document to a real estate transaction Upload a document file to a real estate transaction CLI equivalent: proof real-estate documents upload
| Name | Type | Req | Description |
|---|---|---|---|
| file-path | string | yes | Positional argument file-path |
| filename | string | – | Document filename |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_templates_list ~70
List templates List all real estate templates for your organization CLI equivalent: proof real-estate templates list
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return (default: 100, max: 1000) |
| offset | integer | – | Number of results to skip for pagination |
No output schema declared.
No examples provided.
real_estate_transactions_cancel ~40
Cancel a real estate transaction CLI equivalent: proof real-estate transactions cancel
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_transactions_create ~73
Create a real estate transaction Create a new real estate transaction CLI equivalent: proof real-estate transactions create
| Name | Type | Req | Description |
|---|---|---|---|
| draft | boolean | – | Create as draft |
| file-number | string | – | File number |
| loan-number | string | – | Loan number |
| type | string | – | Transaction type |
No output schema declared.
No examples provided.
real_estate_transactions_get ~49
Get a real estate transaction Get details of a specific real estate transaction CLI equivalent: proof real-estate transactions get
| Name | Type | Req | Description |
|---|---|---|---|
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_transactions_list ~199
List real estate transactions List real estate transactions with optional filtering CLI equivalent: proof real-estate transactions list
| Name | Type | Req | Description |
|---|---|---|---|
| created-date-end | string | – | ISO-8601 DateTime - transactions created before this time |
| created-date-start | string | – | ISO-8601 DateTime - transactions created after this time |
| document-url-version | string | – | Document URL version (v1 or v2) |
| last-updated-date-end | string | – | ISO-8601 DateTime - transactions updated before this time |
| last-updated-date-start | string | – | ISO-8601 DateTime - transactions updated after this time |
| limit | integer | – | Limit number of results |
| loan-number | string | – | Find transactions associated with loan number |
| offset | integer | – | Offset for pagination |
| organization-id | string | – | Organization ID of child account |
| status | string | – | Filter by transaction status |
No output schema declared.
No examples provided.
real_estate_transactions_place_order ~95
Place order for a real estate transaction Place an order for a real estate transaction CLI equivalent: proof real-estate transactions place-order
| Name | Type | Req | Description |
|---|---|---|---|
| require-new-signer-verification | boolean | – | Require the signer to verify email ownership |
| suppress-email | boolean | – | Don't email the signer on order placement (you must supply transaction_access_link yourself) |
| transaction-id | string | yes | Positional argument transaction-id |
No output schema declared.
No examples provided.
real_estate_verify_address ~97
Verify a street address Verify a street address and get recording jurisdiction information CLI equivalent: proof real-estate verify-address
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City (required) |
| line1 | string | yes | Street address line 1 (required) |
| postal-code | string | – | Postal/ZIP code |
| state | string | yes | State abbreviation (required) |
| transaction-type | string | – | Transaction type for eligibility check |
No output schema declared.
No examples provided.
real_estate_webhooks_create ~72
Create a real estate webhook Create a new real estate webhook CLI equivalent: proof real-estate webhooks create
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | – | Custom header to include in webhook requests |
| subscriptions | array | – | Webhook event subscriptions |
| url | string | yes | Positional argument url |
No output schema declared.
No examples provided.
How do I install the Proof CLI (unofficial) MCP server?
Proof CLI (unofficial) runs locally as a container image, launched with docker run --rm -i -e PROOF_API_KEY -e PROOF_API_ENDPOINT ghcr.io/tsarlewey/proof-cli:0.3.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/tsarlewey/proof-cli
claude mcp add tsarlewey-proof-cli -- docker run --rm -i -e PROOF_API_KEY -e PROOF_API_ENDPOINT ghcr.io/tsarlewey/proof-cli:0.3.1
This image reads PROOF_API_KEY and PROOF_API_ENDPOINT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Proof CLI (unofficial) MCP server?
Proof CLI (unofficial) is an MCP server listed in the public MCP registry as io.github.tsarlewey/proof-cli. Notarize, e-sign, and verify identity with the Proof API. Unofficial; not affiliated with Proof. This page covers its container image (ghcr.io/tsarlewey/proof-cli).
Is the Proof CLI (unofficial) MCP server safe to use?
Proof CLI (unofficial) scores 52 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Proof CLI (unofficial) MCP server expose?
Proof CLI (unofficial) exposes 60 tools: business_documents_add, business_documents_delete, business_documents_get, business_integrations_create, business_notaries_create, and 55 more. Their descriptions and schemas cost roughly 6,362 tokens of context every time the server is loaded.
Is the Proof CLI (unofficial) MCP server still maintained?
Proof CLI (unofficial) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Proof CLI (unofficial) MCP server under?
Proof CLI (unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.