Three.ws Provenance MCP Server

Three.ws Provenance is an MCP integration. Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

Packages and local setup

The published npm package is @three-ws/provenance-mcp, version 0.1.2. Its declared MCP transport is stdio.

The package declares 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 (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related blockchain & web3 MCP servers for tools that cover the same kind of work.