mcpField
D
delta-witness

delta-witness

Local
github.com/15998194110Security0Updated 2d ago

About delta-witness

DELTA Witness is a trust layer for autonomous actions that records timestamped hashes of public sources and uses them for deterministic preflight decisions. It offers paid capture, preflight, and guarded-action pilot products without claiming that source content is truthful.

Key features

  1. 01Capture public pages and preserve hashes
  2. 02Compare observations with prior proofs or rules
  3. 03Settle designated products through x402 v2
  4. 04Bound targets, requests, and storage
  5. 05Send HMAC-signed monitoring check webhooks

Use cases

  1. 01Preserve evidence before browser automation actions
  2. 02Check changes to public prices or supplier terms
  3. 03Add paid checkpoints to monitoring workflows
  4. 04Record source state for autonomous actions

MCP support

The README mentions an MCP server and MCP metadata but does not specify the capabilities the server exposes to clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"15998194110-delta-witness": {
"command": "npx",
"args": [
"-y",
"delta-witness-mcp"
]
}
}
}
Run commandnpx -y delta-witness-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmdelta-witness-mcp0.7.1

Tools

4

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
productenumNocapture | preflight

Details

From the project README

DELTA Witness v0.7

CURRENT OWNER PRICING (2026-09-10): Capture / authenticated Partner Capture / authenticated Partner Preflight / each NEW Watch check = 1 USDC; Public Preflight = 5 USDC; Guarded-Action Pilot = 10 USDC. Read AGENTS.md and docs/pricing-policy-2026-09-10.md before every run. Conflicting old prices, automatic repricing and paid-canary instructions below are superseded. Historical receipts and prepaid obligations are not rewritten.

AllMCPs Listed on mcpservers.org

DELTA Witness is a Trust Layer for Autonomous Actions. It observes public sources, records timestamped hashes, and lets software make deterministic preflight decisions without claiming that a source is truthful.

Production products and current pricing

  • Capture: POST /v1/capture preserves what a public page says now — $1.00 USDC.
  • Public Preflight: POST /v1/preflight compares a fresh observation with prior proof hashes or explicit text rules — $5.00 USDC.
  • Guarded-Action Pilot: POST /v1/guarded-action-pilot provides the higher-value evidence pilot — $10.00 USDC, only promoted for paid use after production verification on Base with the Treasury below.
  • Watch: authenticated resellers can prepay a finite number of checks and receive HMAC-signed webhooks — $1.00 USDC per new check.
  • Partner gateway: authenticated Partner Capture and Partner Preflight are $1.00 USDC per new billable request under the current owner pricing authority.

Direct Capture, Public Preflight, and Guarded-Action Pilot use x402 v2 with Base mainnet USDC. Settlement completes before Browser Run begins. The treasury is receive-only from the application:

0x1990e21bc219696ff7fbc26527dbaed335ac6367

Never place the treasury private key in Worker, CI, source, or chat.

The current owner-authorized public pricing is $1 Capture / $5 Public Preflight / $10 Guarded-Action Pilot; authenticated Partner Capture, Partner Preflight, and each new Watch check are $1. Historical settled/idempotent deliveries and already-prepaid obligations retain their original paid identity; they are not double-charged or retroactively repriced.

Buyer quickstarts

  • APIHub external x402 → DELTA Capture — documented route for existing APIHub buyers, distinct from provider onboarding. 1 USDC is DELTA's upstream price, not the proxy's total debit; confirm markup and buyer approval. No paid end-to-end verification or APIHub listing is claimed.
  • Browser automation → DELTA paid evidence checkpoint — platform-neutral 1 USDC Capture pattern for browser scrapers, monitors, form flows, and multi-step agents; buy a checkpoint only when a public source state becomes consequential.
  • Amazon Bedrock AgentCore payments → DELTA x402 — use the existing 1 USDC Capture as the narrowest paid checkpoint for procurement terms, price/availability, monitoring evidence, or audit records; raise the buyer-side payment limit only when explicitly choosing a higher-priced DELTA product.
  • BrowserAct monitoring → DELTA evidence — keep BrowserAct as the collection layer, then buy 1 USDC Capture only when a public price, availability, supplier term, article, or other source state becomes materially consequential.

Safety and economics

  • Public HTTP(S) targets on ports 80/443 only; credential URLs, private/link-local/metadata networks, private DNS answers, DNS rebinding, and unsafe redirects are rejected.
  • Request, redirect, time, Browser Run, artifact, and storage bounds are enforced.
  • Raw artifacts remain private in delta-witness-proofs; verifier routes expose metadata and hashes and are noindex.
  • Fulfillment is idempotent and a settled payment cannot fulfill a different request.
  • Customer-facing prices are fixed by the current owner pricing policy rather than autonomously changed by modeled cost floors. If actual fulfillment economics become negative, DELTA records a pricing-margin alert for operator review instead of silently inventing a new customer price.

Verify locally

npm ci
npm run verify
npm run bazaar

npm run bazaar performs a read-only scan of the public Bazaar catalog and reports whether DELTA's x402 resource is indexed. It never submits a payment or changes catalog state.

The partner gateway, SDKs, MCP server, and Apify adapter have their own verification commands. The tagged release workflow verifies every artifact, applies D1 migrations, records the current Worker version, deploys core and gateway, then publishes authorized registries.

Production discovery

The known legacy proof remains available at /v1/proofs/56347db8-1aa5-447f-a0e4-3bb052d7aa89. Its historical manifest predates v0.6 self-integrity fields, so the verifier reports legacy_unverifiable rather than inventing certainty.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.