SettlementWitness MCP server
Commit Oct 6, 2026Emits cryptographically signed Settlement Attestation Receipts to prove AI agents completed tasks according to specific requirements.
Also known as nutstrut/default-settlement-verifier, default-settlement-verifier
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Oct 6, 2026
- License
- MIT
What is SettlementWitness MCP?
SettlementWitness emits cryptographically signed Settlement Attestation Receipts to prove AI agents completed tasks according to specific requirements.
Summary generated from the project's README
About SettlementWitness MCP server
SettlementWitness provides a verification protocol designed to generate cryptographically signed Settlement Attestation Receipts. These receipts serve as proof that an AI agent has completed a specific task according to its defined requirements. Developers can use this service to issue receipts with verdicts such as PASS, FAIL, or INDETERMINATE based on the provided task specifications and outputs.
The system operates via a remote API where users submit verification requests through a POST request to the settlement-witness endpoint. It supports an extended signed payload when a counterparty address is included in the request. Users can retrieve issued receipts using a specific receipt_id or browse delivery history through a public wallet receipt explorer. To ensure security, the service provides public verification keys and a key registry to validate Ed25519 signatures.
What you can do with it
- 1Verify AI task completionGenerate a signed receipt to prove an agent met a specific field requirement.
- 2Audit agent performance historySearch for all recent receipts associated with a specific wallet address.
- 3Validate cryptographic signaturesCheck the authenticity of a receipt using public Ed25519 keys.
- 4Monitor verification metricsAccess a public registry and explorer to view settlement data.
Written from the project's README. Every use case is checked against a quote from it.
How to install SettlementWitness MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall SettlementWitness MCP in Claude Code
$ claude mcp add --transport http default-settlement-verifier https://defaultverifier.com/mcpInstall SettlementWitness MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"default-settlement-verifier": {
"url": "https://defaultverifier.com/mcp"
}
}
}Install SettlementWitness MCP in VS Code
.vscode/mcp.json
{
"servers": {
"default-settlement-verifier": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}Install SettlementWitness MCP in VS Code CLI
$ code --add-mcp '{"name":"default-settlement-verifier","type":"http","url":"https://defaultverifier.com/mcp"}'Install SettlementWitness MCP in Codex
$ codex mcp add default-settlement-verifier --url https://defaultverifier.com/mcpInstall SettlementWitness MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.default-settlement-verifier] url = "https://defaultverifier.com/mcp"
Install SettlementWitness MCP in Gemini CLI
$ gemini mcp add -s user --transport http default-settlement-verifier https://defaultverifier.com/mcpInstall SettlementWitness MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"default-settlement-verifier": {
"url": "https://defaultverifier.com/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablenutstrut/default-settlement-verifier is public and reachablegithub.com/nutstrut/default-settlement-verifier ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-06github.com/nutstrut/default-settlement-verifier ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 93 msPass
README
View on GitHubDefaultVerifier — SAR Verification Infrastructure
SAR (Settlement Attestation Receipt) is a verification protocol that produces cryptographically signed receipts proving whether an AI agent completed a task according to its specification.
DefaultVerifier is a live SAR verifier implementation with a public receipt registry, metrics API, and explorer.
If it matters—Verify it.
Architecture
Understand the SAR stack and verification model:
Example Response
{ "witness": "SettlementWitness", "witness_version": "v0", "task_id": "example", "verifier_endpoint": "https://defaultverifier.com/verify", "witness_timestamp": "2026-01-01T00:00:00Z", "receipt_id": "...", "receipt": { "profile": "settlement-witness-verified-v0.2", "task_id_hash": "sha256:...", "verdict": "PASS", "reason_code": "CONDITION_SATISFIED", "ts": "...", "verifier_kid": "...", "counterparty": "0xABC...", "receipt_id": "sha256:...", "sig": "base64url:..." },
"_ext": { "agent_id": "0x123:demo" } }
Notes
- the receipt payload is issued under the
settlement-witness-verified-v0.2profile; verdicts arePASS,FAIL, orINDETERMINATE - when
counterpartyis present, it is included in signature scope and inreceipt_idderivation - retired signer keys remain valid for verifying receipts they historically signed;
verifier_kidin a receipt is historical evidence and is never rewritten - current signer lifecycle (which
kidis active vs. retired) is published athttps://defaultverifier.com/.well-known/sar-keys.json— treat that endpoint, not this README, as the source of truth for which key is currently active - this behavior is implemented and publicly verifiable via the live receipt and key endpoints
SAR Compatibility: This implementation follows SAR verification semantics, with an extended signed payload when counterparty is present.
Demo
Run a full end-to-end verification in ~2 minutes: DEMO.md
Quick Start
1. Create a receipt
curl -X POST https://defaultverifier.com/settlement-witness
-H 'content-type: application/json'
-d '{
"task_id":"quickstart-001",
"spec":{"checks":[{"kind":"field_equals","inputs":{"output_path":"$.result"},"expected":"hello"}]},
"output":{"result":"hello"},
"counterparty":"0x1234567890abcdef1234567890abcdef12345678"
}'
2. Fetch the receipt
curl https://defaultverifier.com/settlement-witness/receipt/<receipt_id>
Note: use the receipt_id from the returned receipt
3. Verify locally (Node)
cd examples/node-verify node verify.js receipt.json jwks.json
Examples
Node.js verification example: examples/node-verify/
Python verification example: examples/verify_receipt_python.py
Usage: python3 examples/verify_receipt_python.py <receipt_id>
API Endpoints
Create Receipt
POST /settlement-witness
Submits a task verification request and returns a signed SAR receipt.
Retrieve Receipt
GET /settlement-witness/receipt/{receipt_id}
Note: Use the receipt_id from the returned receipt (sha256:...) for retrieval.
Returns a previously issued receipt.
Wallet Receipt Explorer
GET /settlement-witness/receipts?wallet={address}
Returns recent receipts associated with a wallet address.
The public explorer is available at:
https://defaultverifier.com/explorer
This interface allows browsing recent receipts and wallet-indexed delivery history.
Public Verification Keys
https://defaultverifier.com/.well-known/jwks.json
Alternative (SAR protocol reference): https://defaultverifier.com/.well-known/sar-keys.json
Used to verify Ed25519 signatures for receipts.
Key Registry
https://defaultverifier.com/.well-known/sar-keys.json
Registry of verifier public keys referenced by verifier_kid.
SettlementWitness MCP questions
How do I add SettlementWitness MCP to Claude Code?
Run claude mcp add --transport http default-settlement-verifier https://defaultverifier.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add SettlementWitness MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What is a Settlement Attestation Receipt (SAR)?
SAR is a verification protocol that produces cryptographically signed receipts proving whether an AI agent completed a task according to its specification.
What are the possible verdict outcomes in a receipt?
The receipt payload uses the settlement-witness-verified-v0.2 profile, where verdicts can be PASS, FAIL, or INDETERMINATE.
How can I find the currently active signer keys?
The current signer lifecycle is published at the official sar-keys.json endpoint.