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.

Gemot Deliberation Server

REMOTE · GEMOT.DEV · 2 COMPONENTS · SCANNED SEP 27

Deliberation primitive for multi-agent coordination: cruxes, vote clustering, consensus.

0 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2447 tokens (~349/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Gemot Deliberation Server MCP server?

Gemot Deliberation Server is a hosted endpoint at https://gemot.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · gemot.dev

# add to Claude Code
claude mcp add --transport http dev-gemot-gemot 'https://gemot.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-gemot-gemot": {
      "url": "https://gemot.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-gemot-gemot": {
      "type": "http",
      "url": "https://gemot.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-gemot-gemot]
url = "https://gemot.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-gemot-gemot": {
      "type": "remote",
      "url": "https://gemot.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-gemot-gemot --url 'https://gemot.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-gemot-gemot:
    url: "https://gemot.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-gemot-gemot": {
      "Transport": "http",
      "Url": "https://gemot.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-gemot-gemot -t streamable-http -u 'https://gemot.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-gemot-gemot": {
      "type": "http",
      "url": "https://gemot.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 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
  • 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 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
    • Schema quality: fair → poor functional
    • New tool “account” functional
  • 7 Aug 26 0
    • Tool “admin” rewrote its description, which is the text the model reads security
    • “decide” added an optional parameter “note” cosmetic
    • “decide” added an optional parameter “dependent_commitment_id” cosmetic
    • “decide” added an optional parameter “accessor_id” cosmetic
    • “admin” added an optional parameter “agent_id” cosmetic
    • “decide” added an optional parameter “kind” cosmetic
  • 5 Aug 26 0
    • Tool “deliberation” rewrote its description, which is the text the model reads security
    • Tool “decide” rewrote its description, which is the text the model reads security
    • Tool “participate” rewrote its description, which is the text the model reads security
    • “deliberation” added an optional parameter “signature_policy” cosmetic
    • “deliberation” added an optional parameter “principal_policy” cosmetic
    • “analyze” added an optional parameter “options” cosmetic
    • “analyze” added an optional parameter “option_votes” cosmetic
    • “participate” added an optional parameter “principal_credential” cosmetic
  • 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
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 27 Sept 2026 · Probed https://gemot.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gemot.dev CN=YE1,O=Let's Encrypt,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA384 574f60c2ee0afc7711e60f20e57e568fcad
SANs: gemot.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of gemot.dev. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
gemot.dev. present 27365 13 Verified
gemot.dev. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gemot.dev/mcp Verified 200
http (plaintext) http://gemot.dev/mcp HTTPS enforced 301 https://gemot.dev/mcp
MCP tools · 7 exposed · ~2,001 tokens

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 →

Tool Tokens
account ~137

Fund your gemot credit balance. Actions: - buy_credits: Top up THIS API key's balance over the ATXP/x402 rail (optional: pack, atxp_account_id, payment_credential). Call once with no payment_credential to receive a payment-required challenge (the x402 accepts to pay against), then call again with payment_credential set to the base64 X-PAYMENT settle credential. Credits are added only on a settled, on-chain-confirmed charge.

NameTypeReqDescription
actionstringyes–
atxp_account_idstring––
packstring––
payment_credentialstring––

No output schema declared.

No examples provided.

admin ~160

Admin and audit tools. Actions: - report_abuse: Report abusive content (deliberation_id, reason) - get_audit_log: Get audit trail incl. tamper-evident log with proofs (deliberation_id) - list_templates: List available governance templates - get_votes: Get all votes (deliberation_id) - get_vote_state: Get your own agent's recorded votes to confirm they landed and whether each is marked relayed vs direct (deliberation_id, agent_id) - replica_pubkey: Get the server's BLS public key for offline proof verification

NameTypeReqDescription
actionstringyes–
agent_idstring––
deliberation_idstring––
reasonstring––

No output schema declared.

No examples provided.

analyze ~523

Analyze disagreements and find common ground. Actions: - run: Trigger analysis — extracts cruxes, clusters, consensus (deliberation_id; optional: model) - get_result: Get analysis result (deliberation_id; optional: round). While the analysis is running, returns {status:"pending", analysis_status: <stage>} with the current pipeline stage (taxonomy / extracting / crux_detection / clustering) so a single poll loop on this tool replaces calling deliberation action:get for progress. - cancel: Cancel in-progress analysis (deliberation_id) - propose_compromise: Generate a compromise statement (deliberation_id; optional: model) - reframe: Restate a position emphasizing common ground (deliberation_id, position_id; optional: model) - challenge: Challenge an analysis result (deliberation_id, agent_id, reason) - dispute_crux: Dispute a crux classification (deliberation_id, agent_id, crux_claim, correction) - expert_panel: Run an adversarial expert panel review (document; optional: topic, source_type, depth, experts, group_id, model). Creates a deliberation, submits expert critiques, triggers analysis. Returns deliberation_id immediately — poll with deliberation action:get for status, then analyze action:get_result. depth: "quick" (~2 min, 3 experts, tight taxonomy) or "thorough" (~7 min, 5 experts, full taxonomy). source_type selects specialized experts: "code_review", "architecture", "experiment", "proposal". - follow_up: Submit follow-up expert positions responding to round 1 cruxes, then trigger round 2 analysis (deliberation_id; optional: model). Experts review the cruxes and consensus, flag misclassifications, and identify missed issues. Requires round 1 to be complete.

NameTypeReqDescription
actionstringyes–
agent_idstring––
correctionstring––
crux_claimstring––
deliberation_idstring––
depthstring––
documentstring––
expertsstring––
group_idstring––
modelstring––
option_votesobject––
optionsnull|array––
position_idstring––
reasonstring––
result_jsonstring––
roundnull|integer––
source_typestring––
topicstring––

No output schema declared.

No examples provided.

coordinate ~196

Multi-agent coordination. Actions: - delegate: Delegate your vote to another agent (deliberation_id, from_agent, to_agent; optional: scope) - invite: Invite an agent to join (deliberation_id, invited_by, invited_agent, reason; optional: role) - generate_join_code: Generate a short-lived join code (deliberation_id; optional: role, ttl_minutes) - join: Join a deliberation using a code (code, agent_id)

NameTypeReqDescription
actionstringyes–
agent_idstring––
codestring––
deliberation_idstring––
from_agentstring––
invited_agentstring––
invited_bystring––
reasonstring––
rolestring––
scopestring––
to_agentstring––
ttl_minutesinteger––

No output schema declared.

No examples provided.

decide ~254

Commitments and reputation tracking. Actions: - commit: Commit to a deliberation outcome (deliberation_id, agent_id, statement; optional: conditional) - get_commitments: Get all commitments (deliberation_id) - fulfill: Mark a commitment as fulfilled (commitment_id; optional: verified_by) — caller must be a participant in the commitment's deliberation, and cannot be the agent that made it - break: Mark a commitment as broken (commitment_id, reason; optional: verified_by) — caller must be a participant in the commitment's deliberation; the committing agent may break its own - reputation: Get an agent's commitment track record (agent_id; optional: group_id)

NameTypeReqDescription
accessor_idstring––
actionstringyes–
agent_idstring––
commitment_idstring––
conditionalstring––
deliberation_idstring––
dependent_commitment_idstring––
group_idstring––
kindstring––
notestring––
reasonstring––
statementstring––
verified_bystring––

No output schema declared.

No examples provided.

deliberation ~283

Manage deliberations. Actions: - create: Create a new deliberation (topic, description, template, group_id, deadline_minutes, rules, visibility, max_participants, type, principal_policy, signature_policy) - get: Get status/stats of a deliberation (deliberation_id) - list: List all deliberations (limit, offset) - list_by_group: List deliberations in a group (group_id, limit, offset) - list_by_agent: List deliberations an agent participated in (agent_id, limit, offset) - delete: Soft-delete a deliberation (deliberation_id) - set_template: Change governance template (deliberation_id, template) - export: Export complete multi-round history (deliberation_id)

NameTypeReqDescription
actionstringyes–
agent_idstring––
deadline_minutesinteger––
deliberation_idstring––
descriptionstring––
group_idstring––
limitinteger––
max_participantsinteger––
offsetinteger––
principal_policystring––
rulesobject––
signature_policystring––
templatestring––
topicstring––
typestring––
visibilitystring––

No output schema declared.

No examples provided.

participate ~448

Participate in a deliberation. Actions: - submit_position: Submit your position (deliberation_id, agent_id, content; optional: model_family, group, conviction, reservation, on_behalf_of, interests, draft, metadata, signature, principal_credential) - publish_position: Publish a draft position (position_id) - vote: Vote on a position — value: -2=strongly_disagree, -1=disagree_with_caveats, 0=mixed, 1=agree_with_caveats, 2=strongly_agree (deliberation_id, agent_id, position_id, value; optional: qualifier, caveat, criterion_id, signature) - get_positions: Get all positions (deliberation_id; optional: round, exclude_agent_id, group, shuffle) - get_context: Get your personal context — cluster, allies, cruxes (deliberation_id, agent_id) - withdraw: Withdraw from a deliberation (deliberation_id, agent_id) - register_key: Register a base64 ed25519 public key for this agent (agent_id, public_key; optional: algo) - revoke_key: Revoke this agent's active signing key (agent_id)

NameTypeReqDescription
actionstringyes–
agent_idstring––
algostring––
caveatstring––
contentstring––
convictionnumber––
criterion_idstring––
deliberation_idstring––
draftboolean––
exclude_agent_idnull|string––
groupstring––
interestsstring––
metadataobject––
model_familystring––
on_behalf_ofstring––
position_idstring––
principal_credentialnull|object––
public_keystring––
qualifierstring––
reservationstring––
roundnull|integer––
shufflenull|boolean––
signaturestring––
valueinteger––

No output schema declared.

No examples provided.

Common questions

What is the Gemot Deliberation Server MCP server?

Gemot Deliberation Server is an MCP server listed in the public MCP registry as dev.gemot/gemot. Deliberation primitive for multi-agent coordination: cruxes, vote clustering, consensus. This page covers its hosted endpoint (https://gemot.dev/mcp).

Is the Gemot Deliberation Server MCP server safe to use?

Gemot Deliberation Server scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Gemot Deliberation Server MCP server expose?

Gemot Deliberation Server exposes 7 tools: account, admin, analyze, coordinate, decide, and 2 more. Their descriptions and schemas cost roughly 2,001 tokens of context every time the server is loaded.

Does the Gemot Deliberation Server MCP server require authentication?

No. We connected to Gemot Deliberation Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Gemot Deliberation Server MCP server still maintained?

Gemot Deliberation Server is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.