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 (13 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 →
real_estate_webhooks_list ~50
List real estate webhooks CLI equivalent: proof real-estate webhooks list
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Limit number of results |
| offset | integer | – | Offset for pagination |
No output schema declared.
No examples provided.
scim_schemas_resource_types ~50
Get resource types Get the supported SCIM resource types for an organization CLI equivalent: proof scim schemas resource-types
| Name | Type | Req | Description |
|---|---|---|---|
| organization-id | string | yes | Positional argument organization-id |
No output schema declared.
No examples provided.
scim_schemas_service_provider_config ~53
Get service provider configuration Get the SCIM service provider configuration for an organization CLI equivalent: proof scim schemas service-provider-config
| Name | Type | Req | Description |
|---|---|---|---|
| organization-id | string | yes | Positional argument organization-id |
No output schema declared.
No examples provided.
scim_schemas_user ~47
Get user schema Get the SCIM user schema for an organization CLI equivalent: proof scim schemas user
| Name | Type | Req | Description |
|---|---|---|---|
| organization-id | string | yes | Positional argument organization-id |
No output schema declared.
No examples provided.
scim_users_create ~130
Create a SCIM user Create a new SCIM user in an organization CLI equivalent: proof scim users create
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the user is active |
| string | – | Email address | |
| external-id | string | – | External ID from SAML provider |
| family-name | string | – | Last name |
| given-name | string | – | First name |
| organization-id | string | yes | Positional argument organization-id |
| roles | array | – | User roles (can specify multiple) |
| username | string | yes | Username (email address) - required |
No output schema declared.
No examples provided.
scim_users_delete ~60
Delete a SCIM user Delete a SCIM user from an organization CLI equivalent: proof scim users delete
| Name | Type | Req | Description |
|---|---|---|---|
| organization-id | string | yes | Positional argument organization-id |
| user-id | string | yes | Positional argument user-id |
No output schema declared.
No examples provided.
scim_users_get ~60
Get a SCIM user Get details of a specific SCIM user CLI equivalent: proof scim users get
| Name | Type | Req | Description |
|---|---|---|---|
| organization-id | string | yes | Positional argument organization-id |
| user-id | string | yes | Positional argument user-id |
No output schema declared.
No examples provided.
scim_users_list ~76
List SCIM users List SCIM users in an organization with optional pagination CLI equivalent: proof scim users list
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Maximum number of results per page |
| organization-id | string | yes | Positional argument organization-id |
| start-index | integer | – | 1-based index of first result |
No output schema declared.
No examples provided.
scim_users_patch ~88
Patch a SCIM user Partially update a SCIM user using PATCH operations CLI equivalent: proof scim users patch
| Name | Type | Req | Description |
|---|---|---|---|
| operation | array | yes | PATCH operations in format 'op:path[:value]' (e.g., 'replace:active:false') |
| organization-id | string | yes | Positional argument organization-id |
| user-id | string | yes | Positional argument user-id |
No output schema declared.
No examples provided.
scim_users_update ~144
Update a SCIM user Update a SCIM user (replaces all fields) CLI equivalent: proof scim users update
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the user is active |
| string | – | Email address | |
| external-id | string | – | External ID from SAML provider |
| family-name | string | – | Last name |
| given-name | string | – | First name |
| organization-id | string | yes | Positional argument organization-id |
| roles | array | – | User roles (can specify multiple) |
| user-id | string | yes | Positional argument user-id |
| username | string | yes | Username (email address) - required |
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.