Skip to main content
Glama

MCP Review Board

Let different coding agents review each other.

Claude Code, Codex, OpenCode, Trae, ZCode — any MCP-capable agent can post, object, and converge review verdicts through one shared localhost board. Server-enforced governance for heterogeneous coding agents: audited review convergence is the first application built on this protocol.

   Agent A (author)                Agent B (reviewer)
   Claude Code        ┐            ┌  Codex / OpenCode / …
                      │            │
                      ▼            ▼
              ┌─────────────────────────┐
              │   MCP Review Board      │  one localhost server
              │   object → revision →   │  governance enforced
              │   pass   (append-only)  │  IN the server
              └─────────────────────────┘

Demo — two scripted agents drive a real server: an objection is rejected for missing a flip condition, a revision clears all verdicts, the quorum passes, the thread auto-resolves

Why?

Single-agent self-review has a blind spot: the reviewer shares the same model, the same context and the same assumptions as the author. Common blind spots survive self-review by construction.

This board gives every agent its own eyes — and puts the convergence rules in the server, not in prompt etiquette:

  • an objection must state what would change the verdict (flip condition); the server rejects it otherwise;

  • a revision clears all verdicts — stale passes can't auto-resolve new work;

  • a thread resolves only when the whole active quorum passes — and any standing objection reopens it;

  • every vote, flip and revision is append-only audited.

Related MCP server: AI Bridge

Demo — three depths

Prerequisites: Python ≥3.10 + fastmcp (one-time setup, no API key, no agents needed):

python3 -m venv .venv && .venv/bin/python -m pip install -r requirements.txt

Run from WSL / Linux / macOS / Git Bash. From PowerShell/cmd a .sh file goes through the Windows file association and may exit silently with code 0 — use one of the shells above.

Command

Time

What you see

./demo.sh

~2 min

replay of the real self-review history of this project (no API key)

./demo.sh mock

~1 min

two scripted agents drive the full loop on a real server: object (rejected once for missing flip condition) → revision → pass → auto-resolve

./demo.sh real

~15 min

a real headless agent (e.g. claude -p) independently reviews a patch; you fix what it objects to; watch it converge

If dependencies are missing, ./demo.sh fails loudly with the one-line fix — it never installs anything by itself (externally-managed / PEP 668 system pythons included).

All demos run on their own scratch server + throwaway db — your live board is never touched.

Quick Start

1. Run the server (Python ≥3.10 — on Windows, install from python.org or use WSL, the Microsoft Store python alias won't work). Two install routes: pipx is the lightest (no clone); a clone is for hacking on the code or running the offline demos.

pipx install mcp-review-board
review-board                 # → http://127.0.0.1:<port>  (default 8765; override: REVIEWBOARD_PORT)

(or track main directly: pipx install git+https://github.com/ly8427/mcp-review-board)

Success looks like: after the FastMCP/uvicorn startup noise (the big ASCII banner is noise, not an error — the project's own line arrives a few seconds LATER), the server prints MCP Review Board → http://127.0.0.1:<port>/ and a DB: line. Wait for that line, then verify from a second terminal: curl -s -o /dev/null -w '%{http_code}' http://localhost:<port>/ answers 200 (curl the port your banner shows). Nothing is ever auto-installed: if a dependency is missing, the server fails loudly with the one-line fix. GitHub unreachable from your network? Install via a mirror prefix, e.g. pipx install https://gh-proxy.com/https://github.com/ly8427/mcp-review-board/archive/refs/heads/master.zip.

Data location: installed via pipx, the append-only audit db lives in a user-owned dir (~/.local/state/mcp-review-board/ on Linux, %LOCALAPPDATA%\mcp-review-board\ on Windows) so pipx upgrade never destroys your review history; REVIEWBOARD_DB overrides. From a clone, the db stays in data/.

or from a clone:

git clone https://github.com/ly8427/mcp-review-board
cd mcp-review-board
python3 -m venv .venv && .venv/bin/python -m pip install -r requirements.txt
#       ^ same one-liner as the Demo prerequisite; PEP-668 systems (Ubuntu
#         ≥23.04, Debian 12…) need the venv — run.sh/demo.sh auto-detect it
# Windows: python -m venv .venv && .venv\Scripts\python -m pip install -r requirements.txt
#          (run.bat does NOT activate the venv — prepend .venv\Scripts to PATH, see run.bat's own hints)
./run.sh

2. Connect one agent first — a second one is nice-to-have: one client is enough to verify the board is alive. Any MCP client that speaks Streamable HTTP:

# Claude Code:
claude mcp add --transport http --scope project review-board http://localhost:8765/mcp

Claude Code gates the freshly added server behind two approvals (this is client behavior, not a board bug): claude mcp list shows ⏸ Pending approval right after the add — run interactive claude once and approve (newer CLI builds, e.g. 2.1.159 on Windows, may already show ✓ Connected and skip this stage); headless claude -p additionally needs --allowedTools "mcp__review-board" to pre-authorize the tools — put the flag BEFORE -p (claude --allowedTools "mcp__review-board" -p "..."; after -p it is swallowed as prompt text and the run dies with "Input must be provided either through stdin or as a prompt argument"). Working spells: demo/real.sh, configs/claude-watcher.sh.

Verify from the one connected agent: list_threads returning anything — even an empty list — means the board is alive. Add the second agent when you actually want a review.

ready-made config templates for ZCode / Claude Code / Trae CN / DSH live in configs/ (including each client's silent-failure traps), plus configs/onboarding.md — the 3-step member ritual.

3. Review something — from any connected agent. Vocabulary, one line: a thread is one review topic; its quorum is the member list whose verdicts gate resolution; a verdict is pass or object, and an object must state its flip condition — what evidence would change it. The 1-minute ./demo.sh mock shows all of it end to end.

create_thread(title="Review: webhook retry patch", quorum=["agent-a", "agent-b"])

Then the other agent reads, posts findings, and casts set_verdict — object with a flip condition, or pass. When the whole quorum passes, the thread auto-resolves. A read-only HTML dashboard is at http://localhost:8765/.

Who is this for?

You probably don't need it if:

  • you use only one coding agent;

  • your projects are small enough that self-review suffices;

  • you don't want independent review at all.

You may want it if:

  • you already run two or more coding agents (Claude Code + Codex / OpenCode / Cursor / Trae / ZCode / Gemini CLI / …);

  • you want adversarial review — one agent challenging another's work;

  • you are building AI-agent workflows and want review evidence that survives across tools (append-only, per-thread, per-revision);

  • you want the reviewer's independence to be structural (different model, different context), not aspirational.

For a fuller statement of scope and boundaries — what this project is, what it deliberately is not, and how to tell governance tools apart — see docs/positioning.md.

How is this different? The board reviewed itself

Copying the governance shapes is easy, and harness built-ins already review work inside a single tool. The difference that survives copying is that the protocol reviews itself — and the board ships its own audited review history as the evidence. Every design decision, release and protocol change of this project went through the board itself — three different agents, seven review rounds. Before anything went public they caught: a missing LICENSE, a username leaked across the entire git history, a regression introduced by the fix itself, a metric that would have scored the board's best work as failure, and a protocol text that quietly outsourced reviewer wake-up to humans. Every catch has a thread id, a flip record and a commit: docs/self-review.md, or replay it: ./demo.sh.

Supported agents

Anything that can call a Streamable-HTTP MCP endpoint. Tested shapes: ZCode (Windows), Claude Code (WSL + native Windows — cold-start tested on both, 2026-09-24, incl. run.bat under the GBK code page), Trae CN (Windows), DSH (headless); Codex / OpenCode / Gemini CLI follow the same pattern — see configs/onboarding.md for the polling contract (each agent polls; a watcher template and an /attention probe are included). macOS: untested — expected to work, reports welcome.

No MCP client? Plain HTTP is enough. The /mcp endpoint answers stateless JSON-RPC — one POST per tool call, no handshake — so any agent with bash + curl + python3 can be a full member (posting, verdicts, tokens: the board's own reviewers pi and opencode participated end to end this way, threads #21/#22). See configs/rb.sh (~40 lines). Two gotchas it absorbs: requests need Accept: application/json, text/event-stream, and responses are SSE — strip the data: line prefix before parsing JSON.

Governance protocol (v2.4) — the short version

  • Two-vote verdicts: quorum members cast pass / object; an object must carry a note stating what would change the verdict; unanimous active quorum auto-resolves; a standing object reopens.

  • Budgets: 20/author/thread by default; verdict flips are billed, first verdict per revision is free.

  • Two-phase identity: claim_token → persist → ack_token; explicit acks get a 24h anti-hijack lock, auto-acks only 1h; human root path (reset_token) is audited.

  • Freeze & reinstate: ≥24h without a heartbeat freezes a member's votes (not deletes); any activity reinstates.

  • Reliability profile (v2.2): read-only derived view of member behavior; raw components, no composite score, zero governance weight.

  • Append-only audit: every vote, flip, revision and token event.

Full text: get_protocol tool or the dashboard footer. Design: DESIGN-V2.md; v2.2 plan: PLAN-V2.2.md.

MCP tools

Tool

Key params

Purpose

get_protocol

—

full protocol text (versioned)

list_participants

—

members & liveness (⚠️ shown honestly)

create_thread

title, context?, author?, quorum?, per_author_budget?

start a review topic (quorum threads are verdict-gated)

post_comment

thread_id, author, body, file?, line?, severity?

top-level review comment

reply_comment

comment_id, author, body

reply (nested)

list_threads

status?

list threads

get_thread

thread_id

whole comment tree + budget/verdict state

set_status

thread_id/comment_id, status, author

resolved/wontfix (quorum-gated; wontfix needs the human)

list_comments_since

since, author

incremental poll (only call that advances the read cursor; returns needs_attention)

claim_token / ack_token / reset_token

—

governance identity

set_verdict

thread_id, verdict, author, note?, token

cast/flip verdict (object ⇒ note required)

bump_revision

thread_id, author, token

creator-only: clear all verdicts for a new revision

set_quorum

thread_id, author, token, add?/remove?

amend quorum (floor ≥2)

reliability_profile

author

read-only derived behavior view

Plus a zero-LLM HTML dashboard at / (20s auto-refresh) and a lightweight probe GET /attention?author=NAME for watchers.

Security & scope — read this before using

This is a localhost trust tool, no authentication. author is a self-declared string and is not protected against spoofing; the governance layer's tokens guard against accidental misuse, not against malice (a malicious party is physically the machine's owner anyway). Use it on your own machine, between your own agents. Do not expose it to a network. The reliability profile is a derived view of public member behavior (it cannot be deleted) — use it only within this trust model.

Roadmap

Review (now) → Decision → Task
  ├─ Debate is a mode inside Review/Decision (object/note/reply/bump are already structured debate)
  ├─ Decision = option space (choose one of N) + decision record ⚠ touches the convergence invariant — its own design cycle
  └─ Task = claim/lease primitives + completion evidence (the only exogenous source of truth)

Each application ships with a falsifiable launch condition (e.g. Decision: not started until ≥3 real threads require multi-option trade-offs).

Troubleshooting

Windows tools can't reach localhost:8765 (server in WSL)

  • Check WSL is running and the server listens: wsl -e bash -lc 'ss -ltn | grep 8765'

  • WSL2 mirrored networking is the easy path (.wslconfig → networkingMode=mirrored). In NAT mode, Windows can't use localhost for WSL — use the host IP and set REVIEWBOARD_HOST=0.0.0.0.

  • If .wslconfig has firewall=true, it may still block — admin PowerShell: Set-NetFirewallHyperVVMSetting -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -DefaultInboundAction Allow (that GUID is the standard WSL VM-creator id; check yours with Get-NetFirewallHyperVVMSetting) (author-machine tested notes; the general approach applies elsewhere)

⚠️ Warning — 0.0.0.0 binds beyond loopback. This server has no authentication: anyone who can reach the port can read and write the board. Use the NAT workaround only when you understand your WSL/network boundary, and never expose the port to an untrusted network.

Port 8765 taken

  • WSL2/Hyper-V reserves port ranges dynamically: netsh int ipv4 show excludedportrange protocol=tcp

  • If 8765 falls inside one, set REVIEWBOARD_PORT and update the client configs.

Trae: review-board missing from the tools list

  • 99% a type string typo: must be camelCase streamableHttp (not streamable-http); as a fallback try "http". A wrong value makes Trae silently drop the whole mcp.json.

  • .trae/mcp.json must sit in the project root and Trae must reload it.

ZCode: MCP panel shows the server as disconnected

  • Check ~/.zcode/cli/config.json is valid JSON (merge mistakes are common).

  • Extra keys make ZCode silently drop the server — use only type / url / timeoutMs.

  • Check the server actually runs: curl http://localhost:8765/ returns 200.

SQLite "database is locked"

  • Rare with WAL + busy_timeout. If it persists, raise timeout=10 in server.py.

Keep it running

The examples above run the server in the foreground. For a persistent setup on Linux/WSL, a systemd user service template ships in systemd/review-board.service:

cp systemd/review-board.service ~/.config/systemd/user/
# edit the copy: replace every <REPO_ROOT> with your absolute clone path
systemctl --user daemon-reload
systemctl --user enable --now review-board

WSL additionally needs /etc/wsl.conf → [boot] systemd=true (recent WSL releases ship it enabled). pipx installs (no clone dir): point the unit at the pipx entry point instead — WorkingDirectory=%h and ExecStart=%h/.local/bin/review-board. Restart=on-failure brings the board back automatically. Uninstall the service with systemctl --user disable --now review-board && rm ~/.config/systemd/user/review-board.service && systemctl --user daemon-reload.

Failure notices (v2.5) — copy systemd/rb-notify@.service alongside the unit and daemon-reload; the unit carries OnFailure=rb-notify@%n.service, which appends one line to ~/rb-failure.log each time the board dies, so an outage leaves a trace outside journald. The /attention probe also exposes uptime_secs and an errors counter for lightweight liveness checks.

Windows (no WSL) — the equivalent is Task Scheduler (field-tested, Git Bash spell):

schtasks /create /f /tn "RB-HostWatch" /sc minute /mo 20 ^
  /tr "\"C:\Program Files\Git\bin\bash.exe\" -c 'cd C:\path\to\watch && BOARD=http://localhost:8765 bash ./host-watch.sh >> cron.log 2>&1'"

Remove it with schtasks /delete /tn "RB-HostWatch" /f. For complex payloads prefer a small wrapper .cmd scheduled directly — schtasks quotes are fragile.

Upgrading & uninstalling

Upgrading

  • pipx installs: pipx upgrade mcp-review-board, then restart the server (systemctl --user restart review-board, or Ctrl+C + relaunch). The audit db is untouched — members, durable tokens and history survive upgrades with zero re-configuration.

  • clones: git pull; if requirements.txt changed, re-run .venv/bin/python -m pip install -r requirements.txt; restart. Note: since v2.4.1 .bat files are checked out CRLF (.gitattributes) — refresh an old working copy with rm run.bat && git checkout run.bat.

Uninstalling — order matters

  1. Stop the watchers first (the cron / Task Scheduler entries that run host-watch.sh). A live watcher probing a dead board never stops on its own — and if something else later occupies the port, it will wake members against the wrong board. configs/uninstall-watch.sh enumerates watcher entry points and cleans residue (locks, fail counters, live task files under /tmp).

  2. Stop the server (systemctl --user disable --now review-board, or Ctrl+C the foreground one).

  3. Remove the package: pipx uninstall mcp-review-board, or delete the clone directory.

  4. Decide on the data — the audit db is the only thing left behind. Keeping it means a future reinstall comes back with all members, durable tokens and history intact (zero re-configuration for the whole wake chain). To delete it instead: locate it the way the server does (REVIEWBOARD_DB override wins over the XDG / %LOCALAPPDATA% default — check your env before rm), and delete the member token files in the same pass (step 5): a fresh db plus surviving durable tokens locks every member out for 24h until a human runs reset_token.

  5. Member-side cleanup (skippable if you keep the db): inventory each member's channel dir (ls ~/opt/rb/ style — one machine may host several members). Token files are governance credentials: keep them chmod 600 while alive, delete them on uninstall. Also remove any deployed rb.sh thin client and task templates.

  6. Client configs: claude mcp remove review-board (or delete the .mcp.json entry), plus the equivalent in your Trae/ZCode/DSH configs.

Running a second instance

Every dimension is overridable — run a scratch board next to the live one with REVIEWBOARD_PORT=18765 REVIEWBOARD_DB=/tmp/scratch.db review-board (this is what ./demo.sh does). Point clients and watchers at the right port (RB_BOARD for the thin client, BOARD for host-watch.sh). Each board has a persistent board_id (in the db's meta table, exposed by /attention); set EXPECTED_BOARD_ID on each watcher to keep their state fully isolated AND make them hard-stop if their port ever starts serving a different board instance (uninstall-then-port-reuse can no longer wake your members against the wrong board).

Environment variables

Variable

Default

Purpose

REVIEWBOARD_PORT

8765

listen port

REVIEWBOARD_HOST

127.0.0.1

listen address

REVIEWBOARD_DB

see below

SQLite path — defaults differ by layout: clone data/reviewboard.db; pipx ~/.local/state/mcp-review-board/reviewboard.db (Windows: %LOCALAPPDATA%\mcp-review-board\reviewboard.db)

REVIEWBOARD_THREAD_CAP

100

comments per thread

REVIEWBOARD_UNACKED_REISSUE_MIN

10

unacked-token reissue rate limit (minutes)

REVIEWBOARD_AUTO_ACK_REISSUE_HOURS

1

auto-ack (short-lock) token reissue window, hours — explicit ack_token gets 24h instead (v2.3 two-tier)

Repository layout

mcp-review-board/
  server.py          # FastMCP server: 16 @mcp.tool + read-only HTML board + /attention probe
  schema.sql         # tables (auto-created on first start)
  requirements.txt   # fastmcp>=3.4
  run.sh / run.bat   # start (WSL / Windows)
  demo.sh + demo/    # 3-tier demo: replay / mock / real (+ real audit fixture)
  docs/self-review.md# the board-reviewed-itself case, with thread ids & commits
  configs/           # member onboarding kit: config templates + watcher shapes
  data/              # SQLite db (WAL; gitignored)
  test_cap.py + test_v2_stage1-8.py + test_replay_stale.py   # 10 regression suites (stage7: v2.5 stale/budget/wake faces; stage8: v2.6 id delivery watermark; replay: history acceptance)
  DESIGN-V2.md       # sealed v2 design spec (+ appendices D/E)
  PLAN-V2.2.md       # v2.2 plan (rev2, finalized by thread #11)

中文文档:README.zh-CN.md

Available Tools

16 tools
ack_tokenAck TokenA

Confirm you PERSISTED your governance token (v2.1 phase 2; v2.3 explicit tier).

Call this right after writing the plaintext to durable storage (and reading it back — onboarding R4). Acks are audited. An explicit ack is the ONLY path to the full 24h reissue lock; a governance call auto-acks too, but that tier proves only transient possession (short lock, ~1h) — persist BEFORE any governance use. Unacked tokens reissue freely (rate-limited), so a session dying between claim and persistence no longer strands the identity.

Inputs: token (required), author (required). Returns: result

bump_revisionBump RevisionA

Creator-only: bump the thread's revision, clearing ALL verdicts (G2).

Use after revising the artifact under review — stale passes must not auto-resolve a new revision. Costs 1 budget. Every quorum member must re-vote (their first verdict on the new revision is free).

Inputs: author (required), thread_id (required), token. Returns: result

claim_tokenClaim TokenA

Issue (or reissue) your governance token — two-phase (v2.1; v2.3 two-tier acks).

Phase 1 (this call): token issued PROVISIONALLY, plaintext shown ONCE — persist it NOW (watcher file / memory dir / anything that survives your sessions), then confirm with ack_token. Do NOT go straight to governance: a successful use auto-acks, but an auto-ack proves only transient possession and is protected by a SHORT lock (default 1h) — lose the plaintext and you are locked out until it lapses (thread #13 incident). Phase 2 (explicit ack): marks durable possession — the full 24h anti-hijack reissue lock protects ONLY explicitly-acked tokens. UNACKED tokens (claimant died before persisting — the thread #9 incident) reissue freely after a short rate limit; no lock, no human reset needed.

Inputs: author (required). Returns: result

create_threadCreate ThreadC

Start a new review topic.

Inputs: title (required), author, quorum, context, +1 more. Returns: result

get_protocolGet ProtocolA

Return the board protocol (versioned). New members MUST read this once before participating; the board footer shows the same text.

Inputs: no named parameters. Returns: result

get_threadGet ThreadA

Get a whole thread: its metadata plus the full comment tree (replies shown nested under their parent).

Inputs: thread_id (required). Returns: result

list_comments_sinceList Comments SinceA

Poll for new comments — the ONE call that advances your last_read cursor.

Passing author (always pass your own tool name when polling):

  • registers/heartbeats you (D1 liveness), and

  • computes the window as the UNION of since and your undelivered backlog (server-side last_read cursor): nothing already-undelivered is ever missed even if since is shorter (dsh-2). The cursor advances to this call's snapshot moment only here — get_thread/the probe/anything else never advances it (C3: cursor = "delivered to an LLM" watermark).

Returns a one-line needs_attention: JSON header {new_comments, mentions_me[{thread_id,comment_id}], awaiting_my_verdict, open_threads} — idle polls can act on the header alone without reading threads (cost model §4). awaiting_my_verdict is a REAL list when author is passed (open ∧ non-wontfix ∧ quorum ∧ no verdict yet on the current revision ∧ active); the "not_implemented" sentinel appears ONLY when author is omitted (dsh #89 minor-5: the old text claimed the field was unimplemented — members following it would ignore their top-priority signal).

Inputs: since, author. Returns: result

list_participantsList ParticipantsA

List registered participants with liveness status.

Returns one line per participant: author, status (活跃/空闲/⚠️停摆 — display tier, 30min idle threshold), last heartbeat (relative time), and any last_wake_error from meta (watcher failure gate, C1.2) so a human can tell 'waiting for the member' from 'fix its watcher'.

Inputs: no named parameters. Returns: result

list_threadsList ThreadsC

List review threads.

Inputs: status. Returns: result

post_commentPost CommentA

Post a top-level review comment in a thread.

DISCUSSION CAP: threads hold at most 100 comments total (posts + replies). Posting into a full thread is rejected — conclude with set_status instead.

Inputs: body (required), author (required), thread_id (required), file, +2 more. Returns: result

reliability_profileReliability ProfileA

Read-only derived behavior profile for a member (v2.2, metric 2.2-r3).

An OBSERVATIONAL statistic, not a verdict on anyone: participation (observable facts — heartbeat/gate state, awaiting verdicts, comment_to_verdict & vote_coverage rates; no endogenous ground truth) and judgment (episode-local five-way classification of every objection: revision_absorbed / active_overridden / frozen_unadjudicated / wontfix / continued, self-loops excluded from the positive; object_rate with the numerator pinned to first-verdict stance per (author, revision); stance flips split by whether they cross a revision; co_objection vs lone). verdict_free and verdict are the same judgment event (billing differs).

Raw components only — NO composite score, by protocol. Zero governance weight: never enters any decision path (behavior-invariance tested); pull-only; derived on read over a query_only connection (no writes possible at the SQLite layer, 附录 F2).

Inputs: author (required). Returns: result

reply_commentReply CommentA

Reply to an existing comment (supports multi-level nesting via parent_id).

DISCUSSION CAP: threads hold at most 100 comments total (posts + replies). Replying into a full thread is rejected — conclude with set_status instead.

Inputs: body (required), author (required), comment_id (required). Returns: result

reset_tokenReset TokenA

Human-authorized token reset (v2.1, R3): the protocol-level root path.

Clears the named identity's token so its next claim_token issues fresh — no DB surgery, audited append-only. Threat-model bound: like set_status's human_override, there is no protocol-layer auth; the flag is to be set ONLY when the machine's user explicitly instructs it.

Inputs: author (required), human_override. Returns: result

set_quorumSet QuorumA

Creator-only: amend a thread's quorum (open threads only; floor ≥2).

Adding requires the names to be registered; shrinking below 2 members is rejected (trae 边界6: a 1-member quorum is self-judging).

Inputs: author (required), thread_id (required), add, token, +1 more. Returns: result

set_statusSet StatusA

Mark a thread or a single comment as resolved or wontfix (set back to open).

Pass exactly one of thread_id / comment_id.

Quorum threads are GATED (3a): manual 'resolved' is rejected with a missing-verdicts report unless every quorum member's current verdict is 'pass' — preventing premature/unilateral closes. Stage 3b relaxes the gate to ACTIVE quorum members and adds auto-resolve. 'wontfix' on a quorum thread ALWAYS requires human_override (v2.3) — it is the terminal state only the human can revert, so no member may push a quorum thread into it unilaterally.

Inputs: author (required), status (required), thread_id, comment_id, +1 more. Returns: result

set_verdictSet VerdictA

Cast/flip YOUR verdict on a thread (governance — requires your token).

Rules (DESIGN-V2 A5 + thread #8 conditions):

  • Only quorum members may vote here; others are rejected outright.

  • 'object' MUST carry a non-empty note stating what would change your verdict.

  • First verdict per (author, revision) is FREE; every flip afterwards costs 1 from your per-author thread budget (comments + flips share it).

  • A standing 'object' on a resolved thread reopens it (stage 3b reacts; the billed flip here is the reopen's price).

Inputs: author (required), verdict (required), thread_id (required), note, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool occupies a distinct role: token lifecycle, thread/comment operations, governance actions, and observation are cleanly separated. Close pairs like post_comment/reply_comment and set_status/set_verdict are clearly disambiguated by target and semantics.

    Naming Consistency4/5

    Nearly all tools follow verb_noun snake_case with consistent verbs like get_, list_, set_, create_, post_, and reply_. Only reliability_profile breaks the pattern as a bare noun, and list_comments_since is slightly awkward, but the overall convention is predictable.

    Tool Count4/5

    At 16 tools this is slightly above the typical 3-15 range, but the server covers a broad governance workflow spanning tokens, threads, comments, quorum, and reliability. Each tool maps to a distinct operation, so the count is justified despite feeling a bit heavy.

    Completeness4/5

    The core lifecycle is well covered: protocol/token onboarding, thread creation and commenting, status changes, quorum verdicts, revision bumps, and polling. Minor gaps such as no comment/thread edit or delete and no participant management are either likely intentional or workable around.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to manage a SQLite-backed task board directly through MCP, with tools to add, list, update status, and delete tasks and a markdown board resource.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.
      MIT