DoneProof MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DoneProof MCPderive acceptance criteria for implementing user authentication"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DoneProof MCP
Convert an implementation objective into explicit acceptance criteria and a fresh, traceable evidence matrix. Completion is derived from active policies, current workspace fingerprints, and an intact hash-linked ledger—not from model confidence.
flowchart LR
A[Implementation objective] --> B[Reviewable criteria draft]
B --> C[Activated evidence policy]
C --> D[Discovered verifiers]
D --> E[Approved verification]
E --> F[Hash-linked evidence]
F --> G{Fresh and sufficient?}
G -->|Yes| H[Complete]
G -->|No| I[Failed or insufficient]Highlights
Host-model criterion proposals that remain drafts until explicitly activated
Evidence policies with required kinds and minimum pass counts
Dynamic verifier discovery from current project manifests
One-time approvals for direct argv verification commands
Workspace fingerprints that make old evidence visibly stale
Separate
observedandattestedprovenanceAppend-only SHA-256-linked evidence ledger with tamper detection
Deterministic completion assessment and Markdown proof reports
Install
uv tool install "git+https://github.com/efficjump/doneproof-mcp.git"
doneproof-mcp --transport stdioFor source development:
git clone https://github.com/efficjump/doneproof-mcp.git
cd doneproof-mcp
uv sync --all-extras --locked
uv run doneproof-mcp --transport stdioGeneric MCP client configuration
{
"mcpServers": {
"doneproof": {
"command": "doneproof-mcp",
"args": ["--transport", "stdio"]
}
}
}No local checkout path is required after tool installation.
Tool workflow
Stage | Tools |
Task state |
|
Criteria |
|
Verification |
|
Evidence |
|
Decision |
|
record_file_evidence returns unknown unless an expected SHA-256 is supplied. File existence alone
does not prove semantic correctness. Manual review remains explicitly labelled as attestation.
Safety model
Project roots are constrained by
DONEPROOF_ALLOWED_ROOTS.Verifier commands must come from current project discovery.
Commands use argv execution, output limits, timeouts, and one-time plan tokens.
Workspace-writing commands need separate approval.
User text and command output are redacted before persistence.
Invalid or tampered evidence ledgers reject further appends.
This server is not an operating-system sandbox. Use an isolated environment for untrusted projects.
Streamable HTTP
doneproof-mcp --transport streamable-http --host 127.0.0.1 --port 8767The default endpoint is http://127.0.0.1:8767/mcp.
Development
uv sync --all-extras --locked
uv run ruff format --check .
uv run ruff check .
uv run mypy src
uv run pytest --cov --cov-report=term-missing
uv buildSee architecture, security policy, and contribution guide.
License
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/efficjump/doneproof-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server