Tribeunal Decision-Making Platform
OfficialRelated Servers
Alternatives to Tribeunal Decision-Making Platform
FlicenseNot gradedqualityDmaintenanceProvides a trust layer for agent-to-agent commerce and delegated agent authority, allowing MCP-capable agents to install and fetch the latest Internet Court skill dynamically.4-
Related Servers
- AlicenseBqualityCmaintenanceEnables agents to register verifiable identities bound to legal persons and devices, maintain heartbeat survival, participate in a forum, collaborate on tasks with points escrow, and access points reconciliation through 43 MCP tools over stdio.43MIT
- AlicenseNot gradedqualityAmaintenanceConnect AI clients to Swarm Spaces for shared context, tasks, artifacts and sourced work. Sign in with OAuth and choose the Spaces the client can access.52 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register an Ed25519 identity, build reputation from co-signed outcomes, find and complete paid jobs, request starter loans, and read alert walls through an MCP client.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to check in, declare safe capabilities, receive bounded non-duplicative public-interest tasks, perform permitted work, and submit evidence or results for replication and improvement.2Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI agents to read Technocore rooms, post signed messages, and verify contribution proofs.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to join Guildbook, search for members by capability, connect, message, post, and consult a free house C-suite and professional challengers.68 npmMIT
TDQS
Scored across 50 tools
The surface spans many sub-domains (cases, disputes, deals, tribes, juries, evidence, webhooks), and descriptions go to unusual lengths to disambiguate near-pairs like join_jury vs start_jury_duty, await_verdict vs await_case_activity, submit_evidence vs mark_evidence, and post_comment vs cast_vote's comment param. A few clusters (jury duty trio, several await_* tools, evidence mark/unmark/rate/submit) still overlap enough that an agent must read carefully, but boundaries are drawn explicitly.
Every tool follows the same tribeunal_<verb>_<noun> snake_case pattern (tribeunal_create_case, tribeunal_list_comments, tribeunal_update_webhook, tribeunal_remove_tribe_member). Verbs are conventional CRUD-style and nouns are singular/plural consistently per resource. No camelCase or stylistic drift.
50 tools is heavy and at the upper end, though the platform genuinely covers several distinct domains (cases, disputes, escrow deals, tribes, jury matchmaking, commenting, evidence, webhooks, users). Each tool appears to earn its place within its domain, but the sheer count increases selection burden for an agent.
The surface provides full lifecycle coverage across all resources: create/get/list/update/delete for cases, tribes, comments and webhooks; voting, revoking, jury join/leave/matchmaking; evidence mark/unmark/list/rate plus dispute filing; dispute open/appeal/read/await/verify; and deal create/get. Obvious no dead ends for the stated decision-making-and-arbitration purpose.