three.ws Provenance MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add provenance-mcp -- npx -y @three-ws/provenance-mcp

{
  "mcpServers": {
    "provenance-mcp": {
      "args": [
        "-y",
        "@three-ws/provenance-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.provenance-mcp]
command = "npx"
args = ["-y", "@three-ws/provenance-mcp"]

{
  "mcpServers": {
    "provenance-mcp": {
      "args": [
        "-y",
        "@three-ws/provenance-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "provenance-mcp": {
      "args": [
        "-y",
        "@three-ws/provenance-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: THREE_WS_BASE (Base 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_MS (Per-request timeout in milliseconds for the ledger reads/appends.), THREE_WS_TOKEN (Bearer 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_KEY (Optional 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.). The author declared them in the registry entry; get the values from the project itself.