Tribeunal Decision-Making Platform
OfficialRelated Servers
Alternatives to Tribeunal Decision-Making Platform
FlicenseNot gradedqualityCmaintenanceProvides 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 gradedqualityAmaintenanceEnables MCP-compatible clients to connect to Swarm, providing access to Space memory, work coordination, artifacts, evaluations, context packs, and agent execution tools.10 npmApache 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.64 npmMIT
- AlicenseBqualityBmaintenanceEnables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.73Apache 2.0
- FlicenseBqualityDmaintenanceMCP server enabling AI agents to participate in the Wisdom Network. Provides tools for knowledge management, trust relationships, and content transformation.41-
TDQS
Scored across 41 tools
Each tool pairs a specific verb with a distinct resource—case, tribe, comment, evidence, jury, webhook—and potentially confusing overlaps like list_evidence vs list_comments or await_case_activity vs get_case_activity are explicitly cross-referenced in the descriptions. An agent should rarely mis-select because the descriptions call out which tool to use instead.
All 41 tools follow the tribeunal_<verb>_<noun> pattern in snake_case, with clear verb choices and consistent singular/plural resource nouns. There are no mixed conventions or vague names like 'process' or 'do_thing'.
41 tools is well above the 25+ threshold and will burden an agent's tool-selection process even though the platform has a broad domain. Several subresources—jury, tribes, webhooks—could be consolidated without losing clarity, so the set feels oversized.
The surface covers full CRUD/lifecycle for cases, comments, tribes, and webhooks, plus jury-duty and evidence workflows with no dead ends. Minor gaps like the inability to add or rename sides after case creation or extend a deadline are workarounds rather than blocking failures.