Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.thebotclub/tribunal

NPM · TRIBUNAL · SCANNED SEP 20

Tribunal — Enterprise Claude Code plugin. TDD enforcement, quality gates, vault of rules and agents.

Available components

0 this week 0 Trust /100

Recent critical change

CVE-2026-41242 affects this package (29 Jul 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security73
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 129 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.thebotclub/tribunal MCP server?

io.github.thebotclub/tribunal runs locally as an npm package, launched with npx -y tribunal. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tribunal

# add to Claude Code
claude mcp add thebotclub-tribunal -- npx -y tribunal
// .cursor/mcp.json
{
  "mcpServers": {
    "thebotclub-tribunal": {
      "command": "npx",
      "args": [
        "-y",
        "tribunal"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "thebotclub-tribunal": {
      "command": "npx",
      "args": [
        "-y",
        "tribunal"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add thebotclub-tribunal -- npx -y tribunal
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thebotclub-tribunal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tribunal"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add thebotclub-tribunal --command npx --arg -y --arg tribunal
# ~/.hermes/config.yaml
mcp_servers:
  thebotclub-tribunal:
    command: "npx"
    args: ["-y", "tribunal"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "thebotclub-tribunal": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tribunal"
      ]
    }
  }
}
# add to Vellum
assistant mcp add thebotclub-tribunal -t stdio -c npx -a -y tribunal
// mcp.json
{
  "mcpServers": {
    "thebotclub-tribunal": {
      "command": "npx",
      "args": [
        "-y",
        "tribunal"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 8 Aug 26 0
    • Dependency health: 0.01 → 0.87 functional
  • 2 Aug 26 0
    • Known CVEs: unverified → fail critical
    • Score status: scored → failed critical
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → 0.01 functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Licence: MIT functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • Malware scan: pass → unverified security
  • 29 Jul 26 0
    • CVE-2026-41242 affects this package: high critical
    • Known CVEs: partial → fail critical
    • Score status: scored → failed critical
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: MIT functional
  • 28 Jul 26 0
    • Known CVEs: unverified → partial security
    • Dependency health: partial → 0.87 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/tribunal@1.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-2pr8-phx7-x9h3 CVE-2026-44294 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-66ff-xgx4-vchm CVE-2026-44293 high yes
GHSA-685m-2w69-288q CVE-2026-44289 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-75px-5xx7-5xc7 CVE-2026-44291 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f38q-mgvj-vph7 CVE-2026-54269 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-fx83-v9x8-x52w CVE-2026-44292 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-jggg-4jg4-v7c6 CVE-2026-45740 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jvwf-75h9-cwgg CVE-2026-44290 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q6x5-8v7m-xcrf CVE-2026-44288 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wcpc-wj8m-hjx6 CVE-2026-48712 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xq3m-2v4x-88gg CVE-2026-41242 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f88m-g3jw-g9cj high yes
GHSA-rgj7-g3m4-5g8c high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 108 packages
Packages resolved 108
Deprecated 1
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.thebotclub/tribunal MCP server?

io.github.thebotclub/tribunal is an MCP server listed in the public MCP registry as io.github.thebotclub/tribunal. Tribunal, Enterprise Claude Code plugin. TDD enforcement, quality gates, vault of rules and agents. This page covers its npm package (tribunal).

Is the io.github.thebotclub/tribunal MCP server still maintained?

io.github.thebotclub/tribunal is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.thebotclub/tribunal MCP server under?

io.github.thebotclub/tribunal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.