title, or add and remove tags with addTags and removeTags. Omit walletAddress when signed in to use the current account.
Why this tool exists
Proofs are durable, and this is how durable work stays tracked. A proof can carry its own lifecycle throughstatus: tags — status:backlog, status:todo, status:in-progress, status:review, status:done — plus workspace:<namespace> tags so multiple apps or teams can share one convention without colliding.
Every tag written here is the exact index that proofable_proofs_get filters by: tags, scope, tagPrefix, tagContains, and full-text search. Write the tag once, retrieve the work anywhere — a different session, a different app, a different agent. Work survives sessions and apps instead of living in one chat’s memory.
Verified content, verifier results, and ownership never change. This tool only writes the retrieval index. Visibility (private, unlisted, listed) and private-proof sharing through signed access grants are separate surfaces: Proofs.
Input
One of
title, addTags, or removeTags is required.
Response
Returns the updated proof ID, its currenttags, title, and an unchanged flag when nothing needed to change.
The full loop
- Do the work — verify, create, link, store. Each action produces a proof.
proofable_proofs_update— set the proof’s title and tags: its status and workspace.proofable_proofs_get— retrieve later by those exact tags,scope,tagPrefix, or full-text search, in any session, any app.- Repeat: update status as work moves (
status:todo→status:in-progress→status:done).
Assistant output
Do:Next
Read proofs
The read side: filter by the exact tags this tool writes.
MCP overview
Install, session flow, and tool map.