Gemot Deliberation Server MCP server
dev.gemot/gemotgemot.devstreamable-httpv0.11.0Scanned
Deliberation primitive for multi-agent coordination: cruxes, vote clustering, consensus.
7 tools: 6 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Gemot Deliberation Server MCP server can do
The Gemot Deliberation Server MCP server is published by gemot.dev, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: account, admin, coordinate, decide and 2 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 0.11.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 6Claude Code: ask
accountFund your gemot credit balance.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...tial set to the base64 X-PAYMENT settle credential. Credits are added only on a settled, o..."
Description, as the server wrote it 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.
adminAdmin and audit tools.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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
coordinateMulti-agent coordination.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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)
decideCommitments and reputation tracking.No findings
Why it is in this group
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
Description, as the server wrote it 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)
deliberationManage deliberations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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)
participateParticipate in a deliberation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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)
Only reads 1Show 1 read-only tool
analyzeAnalyze disagreements and find common ground.No findings
Why it is in this group
- The name "analyze" says "analyze": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://gemot.dev/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://gemot.dev/mcp: tools/list returned 7 tools to an anonymous client, including account (write), admin (write), coordinate (write), decide (write), deliberation (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Infoaccount
The description mentions "credential".
What this check looks forMatched text
description: "...tial set to the base64 X-PAYMENT settle credential. Credits are added only on a settled, o..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.11.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http gemot https://gemot.dev/mcpclaude mcp add --transport http gemot https://gemot.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__gemot__analyze"
],
"ask": [
"mcp__gemot__account",
"mcp__gemot__admin",
"mcp__gemot__coordinate",
"mcp__gemot__decide",
"mcp__gemot__deliberation",
"mcp__gemot__participate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gemot. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.gemot/gemot/verify?hash=282e0aea1ec744e4ae984f113a75c76fa391bd2d51af5bdbccd1d08111f54a29" | jq -e '.changed == false'Pinned hash 282e0aea1ec7, from Nov 11, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.gemot/gemot/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.gemot/gemot)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.
Gemot Deliberation Server MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Gemot Deliberation Server MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Gemot Deliberation Server MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Gemot Deliberation Server MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Gemot Deliberation Server MCP server have?
- 7 tools: 6 write, 1 read. account, admin, coordinate, decide, deliberation, participate and analyze.
Does the Gemot Deliberation Server MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Gemot Deliberation Server MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Gemot Deliberation Server MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.