three.ws Provenance

io.github.nirholas/provenance-mcp

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "provenance-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/provenance-mcp@0.1.3"
      ],
      "env": {
        "THREE_WS_BASE": "https://three.ws",
        "THREE_WS_TIMEOUT_MS": "20000",
        "THREE_WS_TOKEN": "<your THREE_WS_TOKEN>",
        "THREE_WS_SIGNER_KEY": "<your THREE_WS_SIGNER_KEY>"
      }
    }
  }
}
Environment variables
  • THREE_WS_BASEBase URL of the three.ws API that serves the agent-actions ledger. Override only when self-hosting or targeting a preview deployment.
  • THREE_WS_TIMEOUT_MSPer-request timeout in milliseconds for the ledger reads/appends.
  • THREE_WS_TOKENrequiredsecretBearer token authenticating every call — a three.ws API key (sk_live_…) or an OAuth access token. The ledger is owner-scoped: you can read and append actions only for agents your token owns. Required for all three tools. Treat like a password.
  • THREE_WS_SIGNER_KEYsecretOptional 0x-prefixed EVM private key. When set, append_agent_action ERC-191-signs each action so anyone can ecrecover the signer and verify authorship on-chain. A per-call `signer_key` arg overrides it. Omit to append unsigned. Treat like cash.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.1.3
Registry
active
Published
10/10/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that three.ws Provenance is listed here — it’s also the link we check for a free listing.

three.ws Provenance — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-nirholas-provenance-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="three.ws Provenance — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![three.ws Provenance — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-nirholas-provenance-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.