Developer · Local MCP server
Proof CLI (unofficial)
Notarize, e-sign, and verify identity with the Proof API. Unofficial; not affiliated with Proof.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tsarlewey/proof-cli- Version
- 0.3.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- tsarlewey (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tsarlewey) · how
- Repository
- github.com/tsarlewey/proof-cli
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/tsarlewey/proof-cli:0.3.1 | - | stdio |
How to connect Proof CLI (unofficial)
Proof CLI (unofficial) runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/tsarlewey/proof-cli:0.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e PROOF_API_KEY -e PROOF_API_ENDPOINT ghcr.io/tsarlewey/proof-cli:0.3.1. It reads these environment variables: PROOF_API_KEY (required, secret) and PROOF_API_ENDPOINT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"proof-cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROOF_API_KEY",
"-e",
"PROOF_API_ENDPOINT",
"ghcr.io/tsarlewey/proof-cli:0.3.1"
],
"env": {
"PROOF_API_KEY": "<secret>",
"PROOF_API_ENDPOINT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| PromptUIBuild a working web app from a prompt, then deploy it to a live URL. | Remote · HTTPLive check: ✓ handshake |
| PrompyaiScores your prompts against your real codebase - context-aware prompt intelligence. | Local · stdio |
| PronounceHow engineers pronounce developer jargon - 1,903 confidence-tagged entries with citations. | Local · stdio |
| ProofGovern your AI coding agent: frame the work, review the changes, keep a signed decision record. | Local · stdio |
| ProofFlowAudit infrastructure for AI coding agents with evidence-backed review and policy gates. | Local · stdio |
| ProofhandHuman QA on real phones and browsers for your coding agent. Pass/fail per step, with screenshots. | Remote · HTTPLive check: sign-in required |
| ProofRail MCP Release CertifierMCP deployment checks: required tools, schema drift and verifiable receipts. Free preflight. | Remote · HTTPLive check: ✗ no handshake |
| Protectwith KbAI-security knowledge as MCP: standards-mapped tools (OWASP, NIST, MITRE) for AI agents. | Remote · HTTPLive check: ✗ no handshake |