Default Settlement Verifier

You learn how to use the Default Settlement Verifier MCP server to validate settlement claims against deterministic rules, receiving a signed, replayable verdict. This guide shows practical usage patterns, how to install dependencies if needed, and how to interact with the MCP endpoint and the SettlementWitness tool to integrate neutral, post-task verification into automation and settlement workflows.

How to use

You interact with the Default Settlement Verifier MCP server through its HTTP MCP endpoint and its stateless SettlementWitness wrapper. The MCP endpoint accepts structured verification requests and returns a signed verdict that you can replay for auditing and dispute reduction. Use the SettlementWitness wrapper to obtain a replay-stable receipt for agent workflows.

Key endpoints you will use:

• POST to the canonical MCP URL to submit a verification claim
• POST to the SettlementWitness endpoint to obtain a replay-stable receipt
• GET the manifest to understand supported capabilities and versioning
• Optional health endpoint to check availability

How to install

Prerequisites: you need network access to the verifier host and a basic HTTP client. If you plan to automate, a simple HTTP client or command-line tool is sufficient.

Step 1: Ensure you can reach the verifier over HTTPS behind your network gateway. The MCP server is exposed at the canonical endpoint for verification.

Step 2: Interact with the endpoints using a command-line HTTP client. The following commands demonstrate common usage patterns. Use your own task identifiers and specifications as you integrate into your workflow.

Step 3: Validate responses and store the signed receipts for auditing and replay verification.

Additional sections

Security and settlement gating: The verifier provides deterministic PASS/FAIL verdicts and signed receipts to support post-task settlement decisions without enforcing custody or payments. Use these receipts to gate downstream actions or settlements in an automated workflow.

Determinism and signatures: Identical inputs produce identical verifier signatures and receipts, while timestamps may vary for observability. The receipt identifier remains stable for identical inputs.

Endpoint behavior: POST to /verify works; POST to /settlement-witness works; GET to /manifest works. GET on settlement-witness is designed to return 405.

OpenClaw compatibility: SettlementWitness includes a drop-in skill that calls the public endpoint and provides a path to integration with OpenClaw skills without running local services.

Agent wrappers and skills: SettlementWitness operates as a stateless wrapper and is compatible with agent frameworks and MCP invocation patterns, enabling replay-stable verification within automated workflows.

Deployment notes: The verifier and SettlementWitness are served via HTTPS behind a reverse proxy, with API routes cache-bypassed to ensure fresh responses. Ensure proper TLS configuration and access controls in your environment.

Non-goals: The system does not act as an oracle, store funds, enforce payments, or provide identity or reputation services. It strictly returns signed verification receipts for post-task validation.

License and contact: The project and its MCP components are distributed under the MIT License. For updates and discussions, you may refer to the project contact channel for announcements and queries.

Endpoints and examples

POST https://defaultverifier.com/verify

{
  "task_id": "example-001",
  "spec": { "expected_output": "hash_or_descriptor" },
  "output": { "expected_output": "hash_or_descriptor" }
}

Available tools

settlement_witness

A stateless wrapper that calls the Default Settlement Verifier MCP endpoint and returns a replay-stable receipt for agent workflows.