Settlement Witness MCP server
{
"mcpServers": {
"defaultverifier-settlement-witness": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}{
"mcpServers": {
"defaultverifier-settlement-witness": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}{
"mcpServers": {
"defaultverifier-settlement-witness": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}{
"servers": {
"defaultverifier-settlement-witness": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}{
"mcpServers": {
"defaultverifier-settlement-witness": {
"type": "http",
"url": "https://defaultverifier.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Settlement Witness is an MCP adapter that emits cryptographically signed Settlement Attestation Receipts (SARs) proving whether an AI agent completed a task according to its specification. It is for developers who need to verify task completion and maintain a public receipt registry.
- Submit a task with expected output conditions and receive a signed receipt confirming pass/fail/indeterminate verdict.
- Retrieve and verify previously issued receipts using public Ed25519 keys and local verification code.
- Query recent verification receipts by wallet address to audit task completion history.
Tools this server exposes
| Tool | Does |
|---|---|
| create_receipt | Submit a task verification request with task_id, specification checks, output, and optional counterparty; returns a signed SAR receipt. |
| retrieve_receipt | Fetch a previously issued receipt by its receipt_id (sha256 hash). |
| query_wallet_receipts | Retrieve recent receipts associated with a specific wallet address. |
| get_verification_keys | Fetch the current set of public Ed25519 keys (JWKS format) used to verify receipt signatures. |
| get_key_registry | Retrieve the SAR protocol key registry showing active and retired signer keys by verifier_kid. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.