MCP Server MCP

three.ws Provenance

By github 👁 1 views ▲ 0 votes

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

Homepage Verified source GitHub

Install

npx -y @three-ws/[email protected]

Configuration Example

{
  "remotes": [],
  "packages": [
    {
      "registryType": "npm",
      "identifier": "@three-ws/provenance-mcp",
      "version": "0.1.2",
      "runtimeHint": "npx",
      "transport": {
        "type": "stdio"
      },
      "environmentVariables": [
        {
          "description": "Base URL of the three.ws API that serves the agent-actions ledger. Override only when self-hosting or targeting a preview deployment.",
          "format": "string",
          "default": "https://three.ws",
          "name": "THREE_WS_BASE"
        },
        {
          "description": "Per-request timeout in milliseconds for the ledger reads/appends.",
          "format": "number",
          "default": "20000",
          "name": "THREE_WS_TIMEOUT_MS"
        },
        {
          "description": "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.",
          "isRequired": true,
          "format": "string",
          "isSecret": true,
          "name": "THREE_WS_TOKEN"
        },
        {
          "description": "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.",
          "format": "string",
          "isSecret": true,
          "name": "THREE_WS_SIGNER_KEY"
        }
      ]
    }
  ]
}

mcp model-context-protocol npm