← Index

three.ws Provenance

io.github.nirholas/provenance-mcp·v0.1.0·Monitoring & Logs

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

Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

Environment variables
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
requiredsecret

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
secret

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.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
25
installability
25
documentation
15
stability
5
Alternatives in Monitoring & Logs