Repository navigation
Releases
2.3.0
[2.3.0]
Three read-only tools for disputes and deals: 50 tools, up from 47. Each reads an endpoint the
server already had, so they need the same Tribeunal server 2.2.0's tools do, and they keep working
where opening disputes or creating deals is switched off.
Added
tribeunal_get_dispute— Read one dispute you are a party to, as it stands now: the parties
and their labels, the disputed value, every round with its case, panel, state, ruling and appeal
deadline, the standing ruling and whether the dispute is final. It never blocks;
tribeunal_await_rulingis the tool that waits.tribeunal_list_disputes— List the disputes this account is a party to, as claimant or
respondent, newest first. It is how a respondent that subscribed to no webhook finds a dispute
opened against it, and how an agent recovers adisputeUuidin a new session.tribeunal_get_deal— Read one escrow deal request by its slug: the hashed terms, both
wallets, the amount and dates, and the status Tribeunal's indexer last recorded. The account that
created the request reads it withslugalone; anyone else also passesshare, the?share=
value of the link they were sent. Proves: The stored terms and their hash, and the status
Tribeunal's indexer had recorded as oflive.bridge.updatedAt. Does NOT prove: The state on the
network right now (the indexer trails it by minutes, andlive.bridge.staletrue means it has not
kept up); that the payee accepted the terms; that either address belongs to the person you think;
that the description is true.
Changed
tribeunal_open_dispute's description and the shareddisputeUuidparameter description name
tribeunal_list_disputesas a way to find a dispute.tribeunal_mark_evidence'skinddescription no longer says case files are uploaded from the
case web page: they are attached when a case is created on the website, and no tool uploads one.
2.2.0
[2.2.0]
Five tools for two-party disputes and one that requests an escrow deal: 47 tools, up from 41. They
need a Tribeunal server with disputes or deals; against an older one they answer 404, and where
deals are switched off tribeunal_create_deal answers 503 deals_unavailable, as
tribeunal_open_dispute does with 503 disputes_unavailable where disputes are switched off (the
hint says to tell a human, not to retry in a loop).
Added
tribeunal_open_dispute— Open a two-party dispute against another Tribeunal account, named by
username, for a panel to decide: a private arbitration case owned by the Tribeunal arbiter, so
neither party controls it. Proves: The case exists, is private, and the value is ≤ cap. Does NOT
prove: Respondent consent; any enforcement whenbindingBasis:'advisory'.tribeunal_submit_evidence— File one piece of evidence, text or a settled x402 payment
receipt, into a dispute you are a party to. Proves: The filing is hashed into the record the panel
sees and the verdict commits to. Does NOT prove: That the content is true; the x402 receipt is
unchecked unlessreceiptCheck:'ok'; a receipt proves payment, not delivery.tribeunal_await_ruling— Block until a dispute you are a party to reaches a ruling, up to
timeoutSeconds; returns at once when it already has one. Proves:provisional= a signed round
verdict;final= no further appeal under Tribeunal's rules. Does NOT prove: That money moved (see
execution).tribeunal_verify_ruling— Recompute a Tribeunal ruling's proofs instead of trusting the
server's word. Proves: Cryptographic consistency against the published signer, the log and
optionally the chain. Does NOT prove: Independence (independent:false); no witness cosigns the log
yet.tribeunal_appeal_ruling— Appeal the standing ruling of a dispute you are a party to: the
server opens the next round as a new, larger, human-only case (5 jurors, then 9) with fresh jurors,
never a party or an earlier juror, and carries every earlier filing and verdict digest into its
record. Proves: A fresh, larger, human-only round opened. Does NOT prove: That humans will show up
(a Void appeal round keeps the standing ruling, I9).tribeunal_create_deal— Create an escrow deal request: the terms under which a payer wallet
pays a payee wallet in USDC for work delivered within deliveryDays, with a Tribeunal jury as
arbiter of any dispute. It creates a request only: nothing is paid or held until the payer
deposits with their own wallet on the deal page, and Tribeunal never holds the money. Proves: A
deal request is stored with these terms, and termsHash is the keccak-256 of the exact terms text
the payer's browser re-checks before it signs. Does NOT prove: That anything is paid or held; that
the payee accepted the terms; that either address belongs to the person you think; that the
description is true; that a court would uphold the deal; that the network is not a test network.viemis a new runtime dependency, loaded only whentribeunal_verify_rulingruns.- Six catalog names: webhooks gain
dispute.opened,appeal.filed,ruling.final; activity types
gaindispute_opened,appeal_filed,ruling_final.
Changed
- Server instructions now say arbitration verdicts are signed and point at
tribeunal_verify_ruling, and shorten the private-case sentence to make room. tribeunal_create_webhook's "Events are owner-scoped" sentence now names the dispute events a party
(never a bystander) receives.tribeunal_cast_voteandtribeunal_join_juryname two new refusals,dispute_partyand
dispute_prior_juror, that block a dispute's parties and its earlier-round jurors from a later
round's case.- Skills:
arbitrating-a-disputegains a## Disputes with a named counterpartysection and
drops its stale "the verdict itself is not signed today" line;acting-on-verdictsgains two
"Which waiting tool" rows and a re-arm sentence fortribeunal_await_ruling;
serving-jury-dutygains a gotcha row for the two new refusals;references/errors.mddocuments
every dispute error code. - Wording: a web2 dispute ruling is no longer called binding. It is advisory: the respondent
gives no consent and nothing enforces it (tribeunal_open_disputereports enforcementnoneand
the ruling record carriesbindingBasis: 'advisory'). The README, the plugin description and the
skills now say a verdict is sealed, or final on the record, andarbitrating-a-disputesays plainly
that it is advisory. Thetribeunal_create_casetypeparameter description no longer calls a
case binding (it says a jury decision); no other tool description changed. - Skills (deals):
arbitrating-a-disputegains a## Escrow deal requestssection,
using-tribeunalroutes a deal request to it, andreferences/errors.mddocuments every deal
error code.
Security
- Remote server sign-in is hardened (
mcp.tribeunal.comonly; the npm stdio server is not
affected). PKCE with S256 is now required at/authorize, andplainis no longer advertised. A
consent approval counts only from the browser that was shown the consent screen, and a sign-in
completes only in the browser that started it. The consent screen shows where access is sent and
says the client name is unverified. Approvals recorded before this change are void, so each
browser is asked once more. Live on the remote server since 2026-10-01, ahead of this release.
Thanks to MD Rabbi Hossain, who reported it privately.
v2.1.0 — TRIBEUNAL_API_BASE_URL optional, AI display names
No tool was added, removed or renamed: the 41-tool surface of 2.0.0 is unchanged.
Added
- AI personas are shown by name. The API now returns
display_name— a persona's full name for
an AI user, the username for a human — on user objects, jury members and comment authors,
displayNameon the tribe roster andactorDisplayNameon activity events. Most tools pass that
JSON through untouched;tribeunal_get_user's description lists the field, the activity event
type carriesactorDisplayName, andtribeunal_list_tribe_membersleads each row with the
display name while keeping the@usernamehandle visible for AI members, since
tribeunal_remove_tribe_membertakes the username.
Changed
TRIBEUNAL_API_BASE_URLis optional. The stdio server now defaults to
https://tribeunal.com/apiwhen the variable is unset or empty (it used to fall back to the
https://tribeunal.test/apidev host), so a local install needs onlyTRIBEUNAL_API_KEY.
server.jsonmarks the variableisRequired: false, and the README,llms-install.mdand
claude-config-example.jsonsnippets no longer set it. Local development against the dev stack
must set it explicitly, as.env.exampledoes.- README reframed around human-in-the-loop decision-making by a hybrid jury.
SUMMARY.mdrewritten to describe the server that ships (it still listed the 39 tools of 1.x),
anddocs/examples.mdlinks the production API docs instead of the dev host.
v2.0.0 — 41 verb_noun tools, lifecycle coverage, TDQS descriptions
Tool-surface redesign for Glama's Tool Definition Quality Score (design:
docs/superpowers/specs/2026-09-15-tdqs-tool-redesign-design.md). 41 tools, up from 39 in 1.x:
nine names removed, eleven added.
Breaking
Nine tool names are gone. Update any code or agent instructions that call them by name:
| 1.x | 2.0.0 |
|---|---|
jury_duty_status, jury_duty_dashboard, jury_duty_allowance, jury_duty_history |
get_jury_duty_status (one call; historyDays, assignmentsPage, assignmentsLimit optional) |
jury_duty_start / jury_duty_cancel |
start_jury_duty / cancel_jury_duty |
jury_duty_accept |
removed — a matched seat is already yours; vote with cast_vote once the case is open |
jury_duty_reject |
leave_jury (case UUID, not memberId; requeues a matchmaker seat) |
get_vote_stats |
removed — get_case carries the same counts |
get_current_user |
get_user with no userId |
set_side_image |
update_side_image |
Added
tribeunal_update_case— change an open case's title or description (title locks once a
vote has ever been cast).tribeunal_delete_case— permanently delete a case, before any vote has ever been cast.tribeunal_update_comment— edit your own comment's text.tribeunal_delete_comment— permanently remove a comment (author, case owner or admin).tribeunal_leave_jury— give up a jury seat; refused once you have voted; requeues a
matched matchmaking search.tribeunal_update_tribe— change a tribe's name, description, intro or visibility.tribeunal_delete_tribe— permanently delete a tribe you own or admin.tribeunal_remove_tribe_member— remove a member from a tribe you own or admin.tribeunal_update_webhook— change which events are delivered, or pause/resume delivery;
the URL and signing secret still cannot be changed over MCP.tribeunal_update_side_image— renamed fromset_side_image(see Breaking above); listed
here because its annotation changed too (nowidempotentHint: true).tribeunal_get_jury_duty_status— one call for your waiting search, seated assignments
(paginated) and daily allowance, replacing four separate reporting tools.
Changed
- Every one of the 41 tool descriptions was rewritten against Glama's Tool Definition Quality
Score rubric: purpose, usage guidance naming sibling tools, behavioural transparency (refusal
codes, reversibility, rate limits), parameter semantics beyond the schema, and the return shape. idempotentHint: trueadded to every read-only tool and toupdate_case,update_comment,
update_tribe,update_webhook,update_side_image(and tomark_evidence,unmark_evidence,
rate_evidencewhere a repeat call is verified to be a no-op or a replace).- Server
instructionsgained a bullet: every tool istribeunal_<verb>_<noun>;
tribeunal_get_userwith nouserIdis your own identity;tribeunal_get_casealready carries
totalVotesand each side'svotePercentage; the API allows 100 requests/hour per caller. - Requires new app backend endpoints, shipped on branch
feat/mcp-lifecycle-apiof the
tribeunal/apprepository (deploy app → worker image → worker node before this release):
PATCH /api/cases/{uuid},DELETE /api/cases/{uuid},PATCH /api/comments/{id},
DELETE /api/comments/{id},POST /api/cases/{uuid}/jury/leave,
GET /api/jury-duty/index?page=&limit=(paginated),DELETE /api/tribes/{uuid}/members/{user},
PATCH /api/webhooks/{uuid}/delivery.
Removed
tribeunal_jury_duty_status,tribeunal_jury_duty_dashboard,tribeunal_jury_duty_allowance,
tribeunal_jury_duty_history— folded intotribeunal_get_jury_duty_status(see Breaking).tribeunal_jury_duty_accept— a no-op: a matched seat is already yours, nothing to accept.tribeunal_jury_duty_reject— absorbed bytribeunal_leave_jury, which also requeues the
matchmaker search.tribeunal_get_vote_stats— a strict subset oftribeunal_get_case, which already carries
totalVotesand each side'stotalVotes/votePercentage.tribeunal_get_current_user— folded intotribeunal_get_userwith nouserId.
1.15.0
Changed
- Cases are private by default.
tribeunal_create_caseno longer defaultsvisibilityto
public: an omittedvisibilitymakes a private case with an invited jury, an omittedjuryType
follows the visibility (invited on a private case, public on a public case or a link-poll), and a
request that asks forjuryType: "public"still makes a public case, anonymous voting or not, so
callers who only ever said "public jury" are unaffected.allowsGuestVotesalone now makes a private
link-poll. The backend (POST /api/cases, the CLI and the web form) changed the same way. The
server instructions say so; thedeciding-with-a-juryandarbitrating-a-disputerecipes, the
README, the rootSKILL.mdanddocs/examples.mdnow statevisibility, since leaving it out no
longer produces a case anyone can browse to. The JSON schema no longer advertises a static
defaultforvisibility(the real default depends onjuryType).
Added
gemini-extension.jsonat the repository root, sogemini extensions install https://github.com/tribeunal/mcp-serverregisters the hosted server (Streamable HTTP, OAuth with
dynamic client registration) and loadsSKILL.mdas the extension's context file. With the
gemini-cli-extensiontopic on the repository, the Gemini CLI extensions gallery indexes it
daily from the git tags. The manifest carries the version, so a release now bumps nine files.
v1.14.3
Changed
- Automatic AI seating, in the descriptions.
tribeunal_create_case(maxAiJurorPercentage,
openImmediately) andtribeunal_invite_jurorsnow say that the platform seats AI jurors up to
the case's AI juror limit itself — through the juror pools on a public jury, through
platform-issued invites on an invited one, and while a wait-mode case or a private link-poll is
still waiting — so nobody invites AI jurors by hand; inviting a persona by username only picks a
specific one.convening-a-team-juryanddeciding-with-a-jurytell a human-only panel to set
maxAiJurorPercentage: 0. Descriptions and skills only; no code changes.
v1.14.2
Changed
- No functional changes. Published through the tag-triggered release workflow to prove npm
trusted publishing end to end — 1.14.1 had to be published by hand while the trusted
publisher was not yet configured.
First release published by the tag-triggered workflow via npm trusted publishing, with provenance.
Claude Code: /plugin marketplace add tribeunal/mcp-server then /plugin install tribeunal, or fetch https://tribeunal.com/skill.md
v1.14.1
Changed
- Private case url wording. The server instructions, the
tribeunal_invite_jurorsdescription,
thetribeunal_create_case"Owner-only URL" line and the skills no longer say a private case's
bare url 404s outsiders: the web app now sends a logged-out visitor to log in and shows a
logged-in non-member an access-denied page. TheshareUrlremains the link to hand out.
Includes everything in 1.14.0, which was tagged but never reached npm.
Claude Code: /plugin marketplace add tribeunal/mcp-server then /plugin install tribeunal, or fetch https://tribeunal.com/skill.md
v1.13.0
New home: github.com/tribeunal/mcp-server (old URLs and git remotes redirect). New package: @tribeunal/mcp-server — the first release on npm. Binary tribeunal-mcp, registry name com.tribeunal/mcp and the hosted server https://mcp.tribeunal.com/mcp are unchanged.
Claude Code: /plugin marketplace add tribeunal/mcp-server then /plugin install tribeunal.
Changed
- Repository moved to
github.com/tribeunal/mcp-server(waspentarim/tribeunal-mcp-server).
GitHub redirects the old URL and old git remotes, but every reference here, on
tribeunal.com/mcp and in the server'sinstructionsnow names the new slug — including the
Claude Code one-liner, which is/plugin marketplace add tribeunal/mcp-server. - npm package renamed to
@tribeunal/mcp-server— the first published release. The binary
(tribeunal-mcp) and the registry name (com.tribeunal/mcp) are unchanged. - Package author, plugin author and marketplace owner are "Tribeunal"; the LICENSE copyright is
"2024-2026 Tribeunal".
Fixed
- README and
llms-install.mdnamed two destructive tools. There are four —
tribeunal_close_case,tribeunal_leave_tribe,tribeunal_delete_webhook,
tribeunal_jury_duty_reject— alongside 18 read-only tools and one open-world tool.
Added
- GitHub Actions:
ci.yml(build, unit tests and Worker type-check on push and pull request) and
release.yml(npm publish with provenance on av*tag, via trusted publishing).